Authentication
Automatically authenticate user information.
Received's APIs use a Bearer token in the Authorization header for each request. This token is obtained after a successful login or registration process and must be securely stored by the client. Ensure the header format is "Authorization: Bearer <your_token_here>", where "<your_token_here>" is replaced with your actual token.
Authenticate API user
Authenticate user and return JWT token for future requests. The JWT token is used to authenticate the user in the API Gateway.
API Login
Responses
JWT token for future requests.
Schema
API Key Generation
API keys serve as unique identifiers to authenticate API clients, ensuring that the client is authorized to access the requested resources. Upon successful login, the API issues a JWT (JSON Web Token) to the client, which encapsulates the user's identity and permissions in a secure format. This JWT can then be used for subsequent API calls, streamlining the authentication process and enhancing security by limiting exposure of sensitive credentials.
Admin Login
Response
Cookie session for further requests with Admin permissions
Generating API key
Response
API keys are critical for securing access to web services, acting as unique identifiers for each user or application. To keep them safe, it's essential to store them securely, avoid sharing them publicly, and use environment variables or encrypted secrets management services to manage them in applications.
Explore More APIs
Delves into additional authentication methods and initial setup instructions, broadening your integration capabilities and enhancing secure access
Admin Logout
List API Keys
Delete API key
Last updated