Automate your links with the GetMySocial API

What can you do with the link in bio API?

1. Create a link with curl

The minimal create call: a shortcode, a type and a destination.

curl -X POST https://api.getmysocial.com/v3/links \
  -H "Authorization: Bearer gms_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "shortcode": "summer",
    "type": "directlink",
    "url": "https://example.com/summer-promo",
    "display_name": "Summer Promo"
  }'

A successful response returns the full link object with its lnk_ id. If the shortcode is already taken you get a 409 with code shortcode_taken: catch it and retry with a different shortcode.

2. Pull a performance table for every link

One request returns pageviews, button clicks, unique visitors and CTR for each link: exactly the table you would otherwise build by hand. Do not loop an overview call per link. This endpoint exists so you never have to.

curl "https://api.getmysocial.com/v3/analytics/links?limit=100&timeframe=30" \
  -H "Authorization: Bearer gms_live_YOUR_KEY"

The timeframe=30 is doing real work: leave it out and every analytics endpoint answers for today only, with no warning. Lists are cursor-paginated, so when the response has has_more: true, pass its next_cursor back as ?cursor=. Resend the same sort with it, or you get a 400 invalid_cursor.

3. Export campaign data straight to a spreadsheet

If your links track URL parameters like utm_source, the API reports on them and exports a real CSV file, ready for Sheets or Excel.

# See which tracked parameters have data
curl "https://api.getmysocial.com/v3/analytics/tracking-params?timeframe=30" \
  -H "Authorization: Bearer gms_live_YOUR_KEY"

# Download the utm_source breakdown as CSV
curl -o utm_source.csv \
  "https://api.getmysocial.com/v3/analytics/tracking-params/utm_source/export.csv?timeframe=30" \
  -H "Authorization: Bearer gms_live_YOUR_KEY"

Parameter tracking is opt-in per link: name the parameters you care about (up to 10) in the link Tracking panel, and every visit carrying them gets recorded from then on. CSV is the one export format the API produces, and it exists only for tracking parameters.

Rules for a well-behaved integration

• Send a timeframe with every analytics call

  Each /v3/analytics/ endpoint answers for today when timeframe is missing. Pass timeframe=7, 30 or 90 for a rolling window. Dates in start_date and end_date are ignored until you also send timeframe_type=custom.

• Treat PATCH as a full replacement

  PATCH /v3/links/{id} validates the body as a complete link payload. display_name is required on every call, and several toggles fall back to their defaults when you leave them out. Fetch the link, change the one field you want, send the whole object back.

• Respect the rate limits

  Reads allow 120 requests per minute, writes 60, each with its own daily budget. Every response carries X-RateLimit headers, and a Retry-After header tells you when to back off.

• Know which reads degrade and which do not

  Cacheable reads keep answering over the limit, serving a slightly stale body with an X-GMS-ApiV3-Degraded header. The CSV export and GET /v3/groups are never cached, so they return a hard 429 the moment you cross the line.

• Use bulk delete for cleanups

  One bulk-delete call accepts up to 100 link ids and counts as a single operation against your quota. Never loop single deletes.

• Treat keys like passwords

  Keep them out of code repositories, use one key per integration so you can revoke narrowly, and rotate a key by creating its replacement before deleting it.

• Handle errors by code, not by message

  Error messages can change; codes like shortcode_taken and plan_required will not. Branch on the code and log the request_id for support.