Request Oauth credentials.

📘

Environment credentials.

Credentials are created per environment, this means that staging credentials cannot be used in production and vice versa.

Third parties already using a specific environment are required to fill out the request form again, to apply for credentials in new environment.

❗️

Sharing credential information.

Never share the credentials with unverified parties, credential owners are responsible for safe storage and sharing procedures of the credentials.

Never share the secret key of a client with any external party.
Zenegy will never ask for the secret key of a client, if such a request is received it should be ignored and reported.

Requesting new credentials.

When requesting credentials, it is important to ensure that all required information is provided. Requests will be denied if the information provided is not valid.
Once the request has been submitted, an e-mail with the credentials or reason for denial will be sent to the contact person defined on the registration form.

Staging credentials.

To request staging credentials, use the form below:

The party using the credentials should fill out the form, not the end users themselves.
It is important to write the correct "application name" and "company name" in the form, as these values will be displayed during authentication.

For staging credentials, the purpose and description of the application do not have to be in-depth, but they will still be used to define the access scopes for the credentials.
Only contact persons saved on the credentials can request changes to the client, and all change requests from non-valid requesters will be denied.

🚧

Handling credentials.

When requesting or handling credentials for the Zenegy API, integrators agree that all security responsibilities and credentials changes will be handled by the integrator themselves and not the customers using the integration.

Mishandling of credentials can result in closure of the client as per the terms and conditions for the API

Production credentials.

To request production credentials, use the form below:

The party using the credentials should fill out the form, not the end users themselves.
It is important to write the correct "application name" and "company name" in the form, as these values will be displayed during authentication.

For production credentials, the purpose and description of the application should be as detailed as possible and will be used to define the access scopes of the client.
Production access requests will be blocked if the purpose and description of the client are not clear or descriptive enough.

Only contact persons saved on the credentials can request changes to the client, and all change requests from non-valid requesters will be denied.

🚧

Handling credentials.

When requesting or handling credentials for the Zenegy API, integrators agree that all security responsibilities and credentials changes will be handled by the integrator themselves and not the customers using the integration.

Mishandling of credentials can result in closure of the client as per the terms and conditions for the API

Requesting credential changes.

Changes to the credentials can be requested by the credentials owner. The possible changes that can be requested are:

• New/updated redirect uri.
• New/updated contact persons.
• Updated application name.
• Updated application company.

Only validated contact persons on the credentials can request changes. All requests from non-valid people will be denied.

Sending the request.

To send a change request, an e-mail should be sent to [email protected] with the following information:

• ClientId.
• Credentials environment.
• Contact person name (if different from requester).
• Contact person e-mail (if different from requester).
• Requested change.

📘

Change request handling.

Make sure to submit a change request as early as possible, the request can take up to five working days to be reviewed, for that reason requests should be sent in good time.

Change requests will not be prioritised due to bad time management of the request.

❗️

Lost credentials

In case of exposed or lost credentials, reach out to our support ASAP