Skip to main content
All API requests to EazeMyAPI must include the API signature key in the request header. This key verifies that the request is authorized to access your project’s APIs.

Required Header

Every API request must include the following header:

JavaScript (Axios)


PHP (cURL)


Python (requests)


cURL


API Key Scopes (Future Vision) (Future Vision)

In the future, EazeMyAPI will support scoped API keys to enhance security and control.

Planned Capabilities

  • Read-only keys (GET requests only)
  • Write keys (POST, PUT, DELETE access)
  • Admin keys (full access)
  • Table-level restrictions (limit access to specific data)
  • Rate-limited keys (control usage per key)

Example (Future Format)

This will allow developers to safely use API keys in different environments (frontend, backend, third-party integrations).

Security Best Practices

  • Never expose the secret key in public repositories
  • Do not store the key inside frontend code
  • Use environment variables to store API keys
  • Rotate keys if compromised

Important Note

The API signature key provides full access to your project APIs. Anyone with this key can perform API operations. Handle it securely. If your application requires user-level security, implement authentication and access control separately.

Framework Examples

React


Next.js


Vue.js


Angular


Flutter (Dart)


Android (Kotlin)


iOS (Swift)