API Documentation

Register a new copyright for an audio file.

Request body multipart/form-data

audio:         [audio file]     required
title:         "Song Title"     required
artist_name:   "Artist Name"    required
artist_id:     "uuid"           required
album:         "Album Name"     optional
release_year:  2025             optional

Or send a URL application/json

If the audio already sits in your own storage, send its URL instead of the bytes. CUA fetches it directly, so you don’t have to download and re-upload the file to register it.

{
  "file_url": "https://yourapp.com/uploads/song.mp3",
  "title": "Song Title",
  "artist_name": "Artist Name",
  "artist_id": "uuid",
  "use_blockchain": true
}

The URL must be publicly reachable over http or https and serve an audio content type. Addresses that resolve to private or internal networks are refused, as are redirects to them.

Response

{
  "success": true,
  "registration_id": "db8fa3d7-0908-46a3-a1a7-d55bd8ce1b24",
  "status": "processing",
  "message": "Registration started"
}

Check the status of a registration. Returns processing while the fingerprint is being generated, then completed or failed. Completion fields appear only once the status is completed.

Response

{
  "registration_id": "db8fa3d7-0908-46a3-a1a7-d55bd8ce1b24",
  "status": "completed",
  "title": "Stand By Me",
  "artist_name": "Logan and Steph",
  "created_at": "2025-12-25T23:21:43.443Z",
  "completed_at": "2025-12-25T23:21:44.749Z",
  "registered_via": "Your Platform",
  "certificate_url": "https://cua.herownsky.com/certificates/db8fa3d7-....pdf",
  "verification_url": "https://cua.herownsky.com/api/v1/verify/db8fa3d7-...",
  "verify_url": "https://cua.herownsky.com/verify/db8fa3d7-...",
  "fingerprint": "SHA256:a00aae06882667de...",
  "blockchain_verified": true,
  "blockchain_tx_id": "0x1e3f..."
}

Notes

• verification_url returns JSON; verify_url is the page a person can open and read.
• registered_via names the platform the work was submitted through, taken from the key that submitted it. It is what the certificate reads: “Your Platform in partnership with CUA, a product of Her Own Sky LLC”. It is null for a key issued to no platform.
• The blockchain fields appear only when the registration was anchored.
• duplicate_of appears when another registration holds byte-for-byte identical audio. It is a file match, not an acoustic one, and not a finding of infringement — registering your own master twice produces the same signal.
• When the status is failed, error carries the reason.

Verify a copyright registration. Returns JSON.

Response

{
  "verified": true,
  "registration": {
    "id": "db8fa3d7-0908-46a3-a1a7-d55bd8ce1b24",
    "title": "Stand By Me",
    "artist_name": "Logan and Steph Vang",
    "registered_at": "2025-12-25T00:00:00Z",
    "registered_via": "Your Platform",
    "fingerprint": "SHA256:abc123..."
  }
}

Download the PDF certificate for a registration.

Response

Returns the PDF file with the appropriate Content-Type headers.

Confirms your key works and tells you which key it is. Useful when a credential was configured a while ago and you need to know what is actually in use. Unlike the other read endpoints, this one requires a key — the credential is the subject of the request.

Response

{
  "success": true,
  "authenticated": true,
  "key_type": "issued",
  "name": "Your Platform",
  "client_id": "eac6d8ee-84e2-4837-bef5-63fd7dfc22dd",
  "partner": {
    "slug": "your-platform",
    "name": "Your Platform"
  }
}

Notes

• key_type is issued for a key issued to you, which can be attributed and revoked on its own.
• partner is the platform your registrations are attributed to and the name printed on their certificates. A null partner means the key authenticates but attributes nothing — worth checking before registering a catalogue.
• An invalid or revoked key returns 401, so this is the quickest way to tell a stale credential from a misconfigured request.