Before you activate
API access belongs to the signed-in account or company workspace. Confirm you are using the right account before creating keys, especially when a team has separate testing and production workspaces.
Do not paste an API secret into frontend code, GitHub issues, screenshots, chat logs, or public documents. Developers should store secrets in backend environment variables.
Activate API access
Log in to Weydub and open Member Center API.
If the account has no key yet, use the API activation button on the page. After activation, the page should show API key status.
Use the UI to confirm the key pair exists. The backend getKS check should return key status without exposing secrets publicly.
Send developers the API docs, task endpoint page, callback rules, and a private secret handoff method.
Developer handoff checklist
- API key and API secret are stored on the backend only.
- The developer has read the quickstart, authentication, async task model, callback, and API reference pages.
- Test tasks use small sample files before production traffic.
- Callbacks are verified in a staging environment before customer-facing release.
- Usage and billing are monitored from Member Center after launch.
Troubleshooting
Refresh Member Center after activation. If the key still does not appear, ask support to check the account's API status.
Confirm the backend signs requests with the correct API key, API secret, timestamp, and endpoint path.
Open billing and usage in Member Center. API tasks use the same product credit balance as web tasks.
Check public network access, HTTPS, firewall rules, and whether the task was created with the expected callback URL.