Connecting customers to my API?

[tyf]

Hey @jeroen welcome to the community!

@jeroen

Is there any sort of documented step-by-step documentation or workflow for this? I can find such steps for creating an application or API, but they all end before the whole third-party access thing.

We unfortunately do not have a step by step guide, but I believe you are on the right track here

@jeroen

If we ever want to grant customers access to some of our other API’s, they should get a new set of client id / client secret for each API. This means for a single customer we should be able to have multiple third-party applications.

You could do it this way, or authorize the existing m2m client for another API.

@jeroen

We can “connect” multiple third-party applications together using an organization. We create these also with the management API. Here I do not see a way to actually connect applications to an organization, is this done with an intermediate step, or some other way?

Unfortunately, I am not aware of any way to to connect applications to organizations so to speak. Are you able to elaborate a bit more on the use case here? You could take advantage of application_metadata if you are just looking for a way to organize which clients/credentials belong to whom.

Here’s an FAQ on the topic for reference:

Auth0 Support for API Keys and Personal Access Tokens

Problem statement: Does Auth0 support the concept of API keys or personal access tokens (think GitHub)? Answer: Auth0 does not provide a solution for personal access tokens. If this is something you are interested in, please upvote this feedback request. Regarding API keys: A client credentials grant is more or less equivalent to an API key - The primary difference being that API keys are typically validated by the API itself whereas client credentials are exchanged for a token at an authoriza…