REST API Authentication

Adeptia's REST API authentication controls who can call your integration endpoints, ensuring that only authorized users and systems can trigger process flows through the platform's REST API layer.

Why authentication matters for integrations

When you expose an integration as a REST API, you need confidence that incoming requests come from legitimate callers. Adeptia lets you choose an authentication approach that matches your security requirements and the capabilities of the systems connecting to your integrations.

Authentication options

Adeptia supports three authentication approaches for REST API access.

Authentication type
Basic
API Key
Kerberos

Basic authentication: user validation options

When you choose Basic authentication, you also select how Adeptia validates the supplied credentials. Three validation modes are available:

Validation mode
Fixed username and password
Database user
LDAP user

This flexibility means you can integrate REST API access control with your existing identity infrastructure, whether that is a standalone credential, a platform-managed user account, or a corporate directory.

Session-based access

In addition to the per-request authentication methods above, Adeptia supports session-based access for REST API calls. When session authentication is enabled, a caller that has already established a valid session with the platform can use that session to authorize API requests, without supplying separate credentials on each call.