Skip to main content

API Security

SWAT APIs support two ways of authentication and managing access to your data.

  • Basic authentication
  • OAuth2
  • Api key authentication

Different groups of APIs may utilize diverse authentication methods to enhance the experience for consumers.

Basic authentication​

APIs beginning with /api/v2 and /api/v2/microservices necessitate basic authentication. SWAT support must establish usernames and passwords. The same authentication technique is employed for the Optimization API located at /api/v1/node_scheduler/.

Api key authentication​

Api key authentication is used by Routing API, specifically /tdroute and /tdtable paths. Api key has to be requested from SWAT support.

Token based authentication​

Consumers who wish to impersonate passengers or drivers via a client-based system can use token-based authentication. This method is more secure and utilizes an OAuth-like authentication system. Endpoints requiring this type of authentication begin with the /passenger/v1 path, while the logging API is accessible at /passenger/v1/sessions.

Tags:
Last updated on