Skip to main content

Base URL

The Moflay API is built on REST principles. We enforce HTTPS in every request to improve data security, integrity, and privacy. The API does not support HTTP. All requests contain the following base URL:
https://api.moflay.com

Authentication

To authenticate you need to add an Authorization header with the contents of the header being Bearer mf_test_1234567890 where mf_test_1234567890 is your API Key.
Authorization: Bearer mf_test_1234567890

Response codes

Moflay uses standard HTTP codes to indicate the success or failure of your requests. In general, 2xx HTTP codes correspond to success, 4xx codes are for user-related failures, and 5xx codes are for infrastructure issues.
StatusDescription
200Successful request.
400Check that the parameters were correct.
401The API key used was missing.
403The API key used was invalid.
404The resource was not found.
429The rate limit was exceeded.
5xxIndicates an error with Moflay servers.
Check Error Codes for a comprehensive breakdown of all possible API errors.

Rate limits

To ensure fair usage and protect the stability of the API, all requests are subject to rate limiting. If your application exceeds the allowed request rate, the API will return a 429 Too Many Requests error response. Learn more about our rate limits.

Pagination

The Moflay API uses cursor-based pagination for all list endpoints. This approach provides consistent and reliable pagination even when data changes frequently. All list endpoints support the following pagination parameters:
  • cursor - A pagination cursor for fetching the next page
  • limit - Number of items to return (1-100, default: 10)
Learn more about our pagination.

Versioning

The Moflay API uses URL-based versioning with the current version being v1. All API endpoints are prefixed with /v1/ to ensure backward compatibility as we evolve the API. The API follows semantic versioning principles and maintains backward compatibility within major versions. When breaking changes are introduced, we’ll release a new major version with appropriate migration guides. Learn more about our versioning.
I