Introducing the Track My Posts API

The Track My Posts API is a RESTful API that provides programmatic access to your workspace data. You can retrieve posts, creators, revenue data, billing information, and more using standard HTTP requests. All endpoints require authentication via API keys and support filtering, sorting, and pagination for efficient data access.

The API follows REST conventions and returns JSON responses. It's designed to be simple to use while providing powerful capabilities for automation and integration. Whether you're fetching data for a custom dashboard or syncing creator information to another system, the API handles it.

All API requests are authenticated using API keys, which you can generate from your workspace settings. Each workspace has its own API keys, ensuring data isolation and security. API keys have the same permissions as your user account, so you can access everything you can see in the web interface.

All API requests require authentication using an API key. Generate API keys from your workspace settings, then include them in the x-api-key header with every request.

API keys are workspace-specific and inherit your user permissions. If you have access to multiple workspaces, you'll need separate API keys for each one. This ensures data isolation and allows you to control access at the workspace level.

Always include the workspaceSlug query parameter in your requests to specify which workspace you're accessing. The API key must belong to that workspace, or the request will fail.

Keep your API keys secure. Never commit them to version control or expose them in client-side code. If a key is compromised, revoke it immediately and generate a new one from your workspace settings.

The Track My Posts API provides endpoints for accessing all major features of the platform. Here's an overview of what's available:

Posts API: Retrieve posts with filtering, sorting, and pagination. Filter by platform, date range, creator, or search query. Perfect for building custom dashboards or syncing post data to other systems.

Creators API: Manage creators programmatically. List all creators, add new ones, update creator information, or remove creators from your workspace. Supports filtering and pagination for large creator lists.

Revenue API: Access revenue attribution data with filtering by date range, creator, or post. Get aggregated revenue metrics or detailed transaction-level data for analysis and reporting.

Workspaces API: Retrieve workspace information, update workspace settings, or manage workspace members. Useful for multi-workspace management or building workspace administration tools.

Billing API: Access subscription status, billing information, and usage metrics. Helpful for building custom billing dashboards or integrating with your internal systems.

Integrations API: List and manage workspace integrations. View connected revenue sources, remove integrations, or check integration status programmatically.

Members API: Manage workspace members, including adding new members, updating roles, or removing members. Supports role-based access control and permission management.

Custom dashboards: Build internal dashboards that display creator performance, revenue metrics, or post analytics in a format tailored to your team's needs. Fetch data from the API and visualize it using your preferred tools.

Automated reporting: Create scheduled reports that pull data from the API and send summaries to stakeholders via email, Slack, or other communication channels. Automate weekly or monthly performance reports.

Data synchronization: Sync creator data, posts, or revenue information to other platforms like CRM systems, analytics tools, or data warehouses. Keep your systems in sync automatically.

Workflow automation: Automate creator onboarding, payout calculations, or performance reviews by integrating the API with your existing tools. Trigger actions based on API data.

Custom integrations: Build integrations with tools that don't have native Track My Posts support. Use the API as a bridge to connect Track My Posts with any system that can make HTTP requests.

Bulk operations: Perform bulk updates or data migrations using the API. Update multiple creators, export large datasets, or import data from other systems programmatically.

Let's walk through making your first API request. We'll retrieve a list of posts from your workspace to demonstrate the basics.

First, you'll need your API key and workspace slug. You can find both in your workspace settings. The API base URL is https://api.trackmyposts.com, and all endpoints are relative to this base.

Here's a simple example using JavaScript to fetch posts:

const response = await fetch(
  "https://api.trackmyposts.com/posts?workspaceSlug=my-workspace",
  {
    headers: {
      "x-api-key": "YOUR_API_KEY"
    }
  }
);

const data = await response.json();
console.log(data);

This request retrieves the first page of posts from your workspace. The response includes pagination metadata, so you can fetch additional pages if needed. You can also add query parameters to filter by platform, date range, or search query.

Most endpoints support filtering, sorting, and pagination. Check the API documentation for each endpoint to see what parameters are available. Common parameters include since and until for date filtering, platforms for platform filtering, and page and limit for pagination.

The API uses standard HTTP status codes to indicate success or failure. Successful requests return 200 OK, while errors return appropriate status codes like 400 Bad Request, 401 Unauthorized, or 404 Not Found.

Error responses include a JSON body with details about what went wrong. Always check the response status and handle errors appropriately in your code. Common errors include invalid API keys, missing required parameters, or permission issues.

Rate limiting applies to API requests to ensure fair usage. If you exceed the rate limit, you'll receive a 429 Too Many Requests response. Implement exponential backoff and retry logic to handle rate limits gracefully.

Most endpoints that return lists support pagination to handle large datasets efficiently. Pagination uses page-based indexing, where you specify a page number and optional limit.

Responses include pagination metadata in the response body, including the current page, total pages, total items, and whether there are more pages available. Use this information to implement pagination in your integration.

The default page size is typically 20 items, but you can adjust this using the limit parameter. Keep in mind that larger page sizes may increase response times, so find a balance that works for your use case.

When fetching large datasets, iterate through pages until you've retrieved all data. Be mindful of rate limits and consider implementing delays between requests if you're fetching many pages in quick succession.

Most list endpoints support filtering and sorting to help you find exactly the data you need. Common filters include date ranges, platform filters, creator filters, and search queries.

Date filtering uses since and until parameters in ISO 8601 format or YYYY-MM-DD format. These filters are inclusive, so posts on the boundary dates are included.

Platform filtering uses the platforms parameter with a comma-separated list of platform names (e.g., tiktok,instagram). This lets you filter posts by specific platforms.

Search queries use the query parameter to search across post captions, mentions, and hashtags. This is useful for finding posts about specific topics or products.

Sorting uses the sortBy and sortOrder parameters. Available sort fields vary by endpoint, so check the documentation for each endpoint's supported sort options.

We're just getting started with the Track My Posts API. We have plans to add more endpoints, webhooks for real-time updates, and additional features based on your feedback. Your input shapes what we build next.

Visit docs.trackmyposts.com to explore the full API documentation, including detailed endpoint descriptions, request/response examples, and data structure schemas.

Generate your first API key from your workspace settings and start experimenting with the endpoints. Begin with simple GET requests to familiarize yourself with the response formats, then build up to more complex integrations.

If you need help or have questions about the API, reach out to support@trackmyposts.com. We're here to help you build powerful integrations with Track My Posts.

Get started with Track My Posts and start building your integration today.