How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Arthur Online Tags API

The Tags API from Arthur Online — 21 operation(s) for tags.

Arthur Online Tags API is one of 32 APIs that Arthur Online publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Tags. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and an AsyncAPI specification.

This API exposes 28 operations across 21 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.arthuronline.co.uk/v2.

28 operations 21 paths 1 schemas 8 GET1 POST19 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.arthuronline.co.uk/v2
Authentication
OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 1

Arthur Online Tags API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (arthurOAuth) using the authorizationCode flow. By default, every request must be authenticated.

  • arthurOAuth — OAuth 2.0 Authorization Code flow. Access tokens are valid for 14 days; refresh tokens for 21 days. Register an application in Arthur Settings OAuth Applicatio…

Paths & Operations 28

Across 21 paths, the API surfaces 28 operations — 8 GET, 1 POST, 19 PUT. Each is listed below with its method, path, parameters, and response codes.

Tags 28
GET
/applicants/{applicant_id}/tags
List Tags on Applicant
listTagsOnApplicant 6 params → 200400401404
PUT
/applicants/{applicant_id}/tags
Tag Applicant
tagApplicant 3 params body → 200400401404
PUT
/applicants/{applicant_id}/untag
Untag Applicant
untagApplicant 3 params body → 200400401404
PUT
/applicants/{applicant_id}/untag_all
Untag All Applicant Tags
untagAllApplicantTags 3 params → 200400401404
GET
/notes/{note_id}/tags
List Tags on Note
listTagsOnNote 6 params → 200400401404
PUT
/notes/{note_id}/tags
Tag Note
tagNote 3 params body → 200400401404
PUT
/notes/{note_id}/untag
Untag Note
untagNote 3 params body → 200400401404
PUT
/notes/{note_id}/untag_all
Untag All Note Tags
untagAllNoteTags 3 params → 200400401404
GET
/properties/{property_id}/tags
List Tags on Property
listTagsOnProperty 6 params → 200400401404
PUT
/properties/{property_id}/tags
Tag Property
tagProperty 3 params body → 200400401404
PUT
/properties/{property_id}/untag
Untag Property
untagProperty 3 params body → 200400401404
PUT
/properties/{property_id}/untag_all
Untag All Property Tags
untagAllPropertyTags 3 params → 200400401404
GET
/tags/{resource}
List Tags On Resource
listTagsOnResource 6 params → 200400401404
POST
/tags/{resource}
Add Tag On Resource
addTagOnResource 3 params body → 200400401404
GET
/tags/{tag_id}
View Tag
viewTag 2 params → 200400401404
PUT
/tags/{tag_id}
Update Tag
updateTag 3 params body → 200400401404
GET
/tenancies/{tenancy_id}/tags
List Tags on Tenancy
listTagsOnTenancy 6 params → 200400401404
PUT
/tenancies/{tenancy_id}/tags
Tag Tenancy
tagTenancy 3 params body → 200400401404
PUT
/tenancies/{tenancy_id}/untag
Untag Tenancy
untagTenancy 3 params body → 200400401404
PUT
/tenancies/{tenancy_id}/untag_all
Untag All Tenancy Tags
untagAllTenancyTags 3 params → 200400401404
GET
/units/{id}/tags
Get Tags on Unit
getTagsOnUnit 1 param → 200400401404
PUT
/units/{unit_id}/tags
Tag Unit
tagUnit 3 params body → 200400401404
PUT
/units/{unit_id}/untag
Untag Unit
untagUnit 3 params body → 200400401404
PUT
/units/{unit_id}/untag_all
Untag All Unit Tags
untagAllUnitTags 3 params → 200400401404
GET
/viewings/{viewing_id}/tags
List Tags on Viewing
listTagsOnViewing 6 params → 200400401404
PUT
/viewings/{viewing_id}/tags
Tag Viewing
tagViewing 3 params body → 200400401404
PUT
/viewings/{viewing_id}/untag
Untag Viewing
untagViewing 3 params body → 200400401404
PUT
/viewings/{viewing_id}/untag_all
Untag All Viewing Tags
untagAllViewingTags 3 params → 200400401404

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (3 properties). Each schema is shown below with its type and property counts.

Error
object
Arthur error envelope.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

arthur-online-tags-api-openapi.yml Raw ↑

Other APIs Arthur Online publishes across the network.

Arthur Online Applicant API
Arthur Online Applicants API
Arthur Online Assets API
Arthur Online Assigned Managers API
Arthur Online Certificates API
Arthur Online Contractor Invoices API
Arthur Online Conversations API
Arthur Online Credit Checks API
Arthur Online Entities API
Arthur Online General Information API
Arthur Online Invite API
Arthur Online Messages API
Where this information came from

This is an independent, third-party profile of Arthur Online Tags API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.