utm-validator

Build and check UTM campaign URLs

Check campaign tagging while preserving existing query parameters. This API never opens the destination URL.

1 credits · USD $0.001

Input schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 2048,
      "x-maxUtf8Bytes": 2048
    },
    "utm_source": {
      "type": "string",
      "maxLength": 200,
      "x-maxUtf8Bytes": 200
    },
    "utm_medium": {
      "type": "string",
      "maxLength": 200,
      "x-maxUtf8Bytes": 200
    },
    "utm_campaign": {
      "type": "string",
      "maxLength": 200,
      "x-maxUtf8Bytes": 200
    },
    "utm_term": {
      "type": "string",
      "maxLength": 200,
      "x-maxUtf8Bytes": 200
    },
    "utm_content": {
      "type": "string",
      "maxLength": 200,
      "x-maxUtf8Bytes": 200
    }
  },
  "required": [
    "url"
  ]
}

Request

curl -X POST 'https://staging.callmint.dev/v1/utm-validator' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Idempotency-Key: unique-request-001' \
  -H 'Content-Type: application/json' \
  -d '{"url":"https://example.com/?ref=launch","utm_source":"newsletter","utm_medium":"email","utm_campaign":"november"}'

Response result

{
  "url": "https://example.com/?ref=launch&utm_source=newsletter&utm_medium=email&utm_campaign=november",
  "valid": true,
  "missing": []
}

Limitations

Requires HTTP(S) without embedded credentials. A valid result means source, medium and campaign are nonblank; it does not measure campaign performance.

All enabled routes accept a JSON object of at most 60,000 UTF-8 bytes. String limits are also measured in UTF-8 bytes.