API Documentation — Automate Your Link Management

Integrate My Backlink into your workflow via REST API. Authenticate with API Keys to query platforms, manage backlinks and projects, and connect browser extensions or automation scripts.

API Key Management

You need to create an API Key before using the API. Each key is prefixed with mlv_ and can have an optional expiration date. Keep your key safe — it is only shown in full once at creation time.

Creating an API Key

Go to the Settings or API Keys page in your dashboard and click Create API Key. Enter a name to identify its purpose (e.g., Browser Extension, Automation Script), and optionally set an expiration date. Copy and securely store the full key immediately after creation — it will only be partially visible afterward. You can delete unused keys at any time.

Authentication

All authenticated API endpoints use Bearer Token authentication. Include your API Key in the Authorization header of each request.

Request Header Format

Authorization: Bearer mlv_your_api_key_here

Never hard-code your API Key in frontend code or public repositories. Use environment variables or a secure secret management solution to store your key.

API Endpoints

Search Platforms

GET/api/v1/platforms

Query the platform directory with category filtering and pagination. This is a public endpoint — no API Key required. Parameters: category (platform category), page (page number), limit (items per page, max 100).

Get User Projects

GET/api/v1/user/projectsAuth Required

Retrieve all projects for the authenticated user, including project name, URL, tagline, and other basic information.

Get User Backlinks

GET/api/v1/user/linksAuth Required

Query the authenticated user's backlink records with project and platform filtering, plus pagination. Parameters: projectId, platformId, page, limit. Returns link details with associated platform and project information.

Create Backlink

POST/api/v1/user/linksAuth Required

Create a new backlink record for the authenticated user. Required fields: url (link URL), title (link title). Optional fields: description, platformId, projectId, anchorText, notes, tags.

Get User Profile

GET/api/v1/user/profileAuth Required

Retrieve the authenticated user's basic information including ID, name, email, and role. Useful for verifying that an API Key is valid.

AI-Assisted Submission Generation

GET/api/v1/ai/generate-submissionAuth Required

Given a link record (linkId), generates AI-assisted submission content suggestions based on the project profile and platform form fields. Returns a prompt and context data (project, platform, field definitions, existing examples).

File Upload

POST/api/v1/uploadAuth Required

Upload image files (JPEG, PNG, WebP, GIF, SVG, max 5MB) via FormData. Specify file (the file), type (logo or screenshot), and optional projectId. Returns the file's access URL and storage key.

Pagination & Filtering

List endpoints support pagination parameters: page (starting from 1) and limit (items per page, default 20, max 100). Responses include a pagination object with total, page, limit, and totalPages. Some endpoints support additional filter parameters such as category, projectId, and platformId.

GET /api/v1/platforms?page=1&limit=20&category=ai-tools

Integration Tip

The platform search endpoint (/api/v1/platforms) requires no authentication, making it ideal for browser extensions. For endpoints that access user data, call them from your server side to keep your API Key secure.