...
- A confidential credential linked to a specific client ID.
- Acts like a temporary password for machine-to-machine authentication.
- Required when requesting a bearer token to connect to the WMDA APIs.
- Expires after a set period. A replacement must be created and used.
- Can be managed by your organisation on the Manage API credentials page Credentials page (see 4. Managing your client secrets below).
...
| Warning |
|---|
Client ID stays the same permanently. It does not expire and does not need to be replaced. Client secret expires after a set period. When the client secret expires, API connections will stop working until a new secret is created and updated in your systems. To avoid interruptions, always rotate the secret before it expires. See 5. Email Notifications About Expiring Client Secrets below |
3. Applications on the Manage API
...
Credentials page:
The Manage API credentials Credentials page lists the applications created by the WMDA IT team for your organisation. Each application represents access to one or more APIs.
Examples of applications you may see on the Manage API credentials Credentials page:
- Partner-NL-OrganisationName-DM
Partner-NL-OrganisationName-SMC
Country Code: 2-letter ISO code for your country (e.g., NL).Organisation Name: your organisation name.API: The WMDA APIs the application has permission to access, e.g.:DM (Data Manager).SMC (Search, Match & Connect
PartnerAlternative-NL-OrganisationName-SMC (sandbox only)
Applications naming convention follows this pattern: Partner-(Country Code)-(Organisation Name)-(API). Where:
)
.
Depending on the API permissions assigned to your application, it may have access to the following WMDA resources:
...