Create events schema

Design your events schema

You can create events schema using the endpoint POST /events/schema.

Authentication

The following header is required for all API calls:

• X-Manufactory-Auth - Manufactory access token

Required keys

• org_id (required) string - Manufactory org ID.
• project_id (required) number - The project ID associated with this schema.
• attributes (required) object - Pairs containing attribute name and the corresponding data type. A complete list of valid data types.

Request example

{
  "org_id": "xyz",
  "project_id": 12345,
  "attributes":{
    "Event name": "TEXT",
    "Event type": "TEXT",
    "Made purchase": "BOOLEAN"
  }
}

Response example

{
  "message": "Events schema created successfully"
}

Related articles

Events > Get events schema

The GET endpoint retrieves event schema details including attribute definitions with data types and display names by specifying organization and project IDs through an authenticated request.

Actors > Create actors schema

The POST /actors/schema endpoint allows creation of actor schemas by specifying organization ID project ID attributes and a unique identifier with proper authentication through a Manufactory access token.

Events > Delete events schema

Event schemas can be deleted through a DELETE request to the endpoint by providing organization ID project ID and authentication via a Manufactory access token.

Manufactory > Events

Event schema design is essential for project implementation requiring single schema per project along with unique API keys to track data across different platforms and applications.