Developer documentation
Subjects
Create and resolve canonical individual and organisation identities without splitting credit history.
Subject types
| Type | Required fields | Useful optional fields |
|---|---|---|
| INDIVIDUAL | minecraft_uuid, current_username | forum_id, discord_id |
| ORGANISATION | legal_name | trading_name, registration_number, website |
A subject ID is RCN's canonical reference. Use it for accounts, inquiries, profiles, reports and disputes. Store the ID after resolution instead of repeating fuzzy searches for every operation.
Resolution workflow
- For an individual, query GET /subjects/minecraft/{minecraft_uuid} when the stable UUID is known.
- Otherwise search GET /subjects?q=… with at least two characters; results include both individual and organisation profiles.
- Confirm the returned type and stable attributes in your own workflow.
- Only create a new subject when no suitable record exists.
- Escalate 409 duplicate signals for review; do not modify identifiers to force creation.
Create an organisation
Shell
curl "https://api.redmontcredit.com/api/v1/subjects" -X POST \
-H "Authorization: Bearer $RCN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"type":"ORGANISATION",
"legal_name":"Example Lending Corporation",
"trading_name":"Example Lending",
"registration_number":"RCR-1042",
"website":"https://example.com"
}'Data minimisation
Report only identifiers required for reliable matching. Do not place secrets, passwords, private messages or unrelated personal information in metadata. Your institution is responsible for a lawful reporting basis and for correcting inaccurate identity data.