No credentials yet? Import the API collections and run any request against the mock environment straight away, with no credentials. Add your OAuth 2.0 credentials when you are ready to call the live API.
Prerequisites
Get the following from D-EDGE before starting:- Token endpoint: the URL of the D-EDGE CRM ID server that issues your tokens.
- OAuth 2.0 credentials: client ID and client secret.
- API base URL: the base URL for your environment.
- Entity identifier: the entity whose guest profiles you manage, a UUID.
Install an OAuth 2.0 library
The token exchange is a plain form POST, so any HTTP client can do it. A library is still worth it: it caches the token and renews it when it expires, which matters here because tokens live 300 seconds. Skip this step if you only use cURL.
Make your first call
Get a token, then send a
POST to the Create a guest endpoint. Each attribute pairs a value with a from field naming who provided the information, and emails takes an object rather than a plain string. The full field list is documented in the Reference.Inspect the response
A successful creation returns Read the profile back with the Get a guest endpoint. Each attribute comes with the source that provided it and the date it last changed, and the CRM fills in what it can infer:See the response schema for the full structure.
200 OK with an empty body and a location header holding the path of the new profile. The last path segment is the guest identifier, which is what you store on your side.Common issues
Next steps
Reference
Endpoint specifications, parameters, and response schemas.
Guidelines
Authentication, request conventions, and response formats.
Best practices
Patterns for clean profiles, from sourcing to deduplication.