Entitlements and Customer Authentication
How Archetype Handles Authentication
When you want to use Archetype's customer authentication framework, currently is done in headers as an
apikey field .
Each customer has a static API key when they're created. Each customer can be assigned multiple API keys and have the ability to reset or add/remove them.
Each endpoint that you've set can be set with a decorator a function to authorize users.
We'll soon allow entitlement access via tagging
We're expanding on custom entitlement to allow permissions to certain datasets and content within endpoints.
When you use the Endpoints object, you can create an endpoint that can authorize different products access to it. That way if you have a premium endpoint gated to only enterprise plans, you can do so on Archetype.
|Headers||Secure way for your users to add their API key to the request.|
If you're looking for JWT or another form of auth for your end users, let us know over at [email protected]
In Archetype you are able to custom define endpoints that you want to assign special rules to.
Endpoints by default have no custom entitlement rules and are authorized as soon as they're subscribed to a plan.
If a customer isn't tracking api calls as a billable metric, the quota value won't be counted.
If a customer's using API calls as a billable metric, defined endpoints can have custom values so a premium endpoint can be valued at 10x a different endpoint.
Endpoints can also be set with entitlements so certain products can have access to premium endpoints.
With Archetype you can create, modify or delete endpoint access privileges on our site or with our REST API.
Updated 6 months ago