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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
SEDNA

SEDNA Contact API API

The Contact API API from SEDNA — 8 operation(s) for contact api.

Documentation Provider Profile APIs.io OpenAPI GitHub

SEDNA Contact API API is one of 17 APIs that SEDNA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Contact API. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 19 operations across 8 paths, and defines 41 schemas. It is described by OpenAPI 3.0.1, at version 2019-01-01.

Requests are made against a single base URL, https://{tenant}.sednanetwork.com/platform.

19 operations 8 paths 41 schemas 4 DELETE7 GET2 PATCH4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
2019-01-01
Base URL
https://example.sednanetwork.com/platform
Authentication
HTTP Basic, OAuth 2.0
Contact
Support
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

SEDNA Contact API API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (Basic). It supports OAuth 2.0 (OAuth) using the clientCredentials flow, exposing 53 scopes. By default, every request must be authenticated.

  • Basic — The basic auth scheme only requires the API-Specific username/password to be set.
  • OAuth — This API prefers OAuth 2 with client credentials flow. You can create your credentials in the Api Credential Management page .

Paths & Operations 19

Across 8 paths, the API surfaces 19 operations — 4 DELETE, 7 GET, 2 PATCH, 4 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Contact API 19
POST
/2019-01-01/contact
Create a new contact Required API Permissions: CONTACTWRITE
createContact body → default
GET
/2019-01-01/contact
Get many contacts Required API Permissions: CONTACTREAD
getContacts 6 params → default
POST
/2019-01-01/contact-group
Create a new contact group Required API Permissions: CONTACTGROUPWRITE
createContactGroup body → default
GET
/2019-01-01/contact-group
Get many contact groups Required API Permissions: CONTACTGROUPREAD
getContactGroups 5 params → default
DELETE
/2019-01-01/contact-group/{id}
Delete a contact group Required API Permissions: CONTACTGROUPDELETE
deleteContactGroup 1 param → default
GET
/2019-01-01/contact-group/{id}
Get a contact group Required API Permissions: CONTACTGROUPREAD
getGroup 3 params → default
PATCH
/2019-01-01/contact-group/{id}
Update a contact group Required API Permissions: CONTACTGROUPWRITE
updateContactGroup 2 params body → default
POST
/2019-01-01/contact-group/{id}/relationships/contact
Add contact(s) to a group Required API Permissions: CONTACTGROUPWRITE
addContactToGroup 1 param body → default
DELETE
/2019-01-01/contact-group/{id}/relationships/contact
Remove contact(s) from a group Required API Permissions: CONTACTGROUPWRITE
removeContactFromGroup 1 param body → default
PATCH
/2019-01-01/contact-group/{id}/relationships/contact
Fully replace a groups contacts Required API Permissions: CONTACTGROUPWRITE
replaceGroupContacts 1 param body → default
DELETE
/2019-01-01/contact/{id}
Delete a contact Required API Permissions: CONTACTDELETE
deleteContact 2 params → default
GET
/2019-01-01/contact/{id}
Get a contact Required API Permissions: CONTACTREAD
getContact 2 params → default
PUT
/2019-01-01/contact/{id}
Update a contact Required API Permissions: CONTACTWRITE
updateContact 2 params body → default
POST
/2019-01-01/contact/{id}/comment
Add comment to the contact Required API Permissions: CONTACTWRITE
addContactComment 1 param body → default
DELETE
/2019-01-01/contact/{id}/comment
Delete contact comment; unsupported at the time Required API Permissions: CONTACTDELETE
deleteContactComment 1 param → default
GET
/2019-01-01/contact/{id}/comment
Get all comments for a contact Required API Permissions: CONTACTREAD
getContactComments 3 params → default
PUT
/2019-01-01/contact/{id}/comment
Update contact comment; unsupported at the time Required API Permissions: CONTACTWRITE
updateContactComment 1 param → default
GET
/2019-01-01/contact/{id}/relationships/contact-group
Fetch a contact's group relationship Required API Permissions: CONTACTREAD
getContactGroupRelationships 1 param → default
GET
/2019-01-01/contact/{id}/relationships/team
Fetch a contact's team relationships Required API Permissions: CONTACTREAD
getContactTeamRelationships 2 params → default

Schemas 41

The contract defines 41 schemas that model the data the API accepts and returns. The most detailed are ContactResourceAttributes (20 properties), ContactCreateAttributes (16 properties), ContactResource (5 properties), ContactGroupResource (5 properties). Each schema is shown below with its type and property counts.

ContactSingle
object
The resource
1 property
ContactResourceAttributes
object
20 properties
ContactCreateAttributes
object
16 properties
ContactGroupCreateResource
object
3 properties
ContactGroupSingle
object
The resource
2 properties
MessageRelData
object
2 properties
TeamRelToMany
object
2 properties
CommentCreateResource
object
Data in contact comment
1 property 1 required
ContactGroupResource
object
5 properties
ContactCollectionLinks
object
3 properties
ContactResource
object
5 properties
ContactGroupRelToMany
object
1 property
ContactPhone
object
3 properties
UserRelData
object
2 properties
CommentSingle
object
Response containing single comment
1 property
ContactRelationships
object
1 property
CommentRelationships
object
2 properties
ContactCollection
object
A collection of resources
2 properties
TeamRelLinks
object
2 properties
TeamRelData
object
2 properties
CommentAttributes
object
2 properties 2 required
ContactGroupAttributes
object
4 properties
ContactCreateRepresentation
object
1 property
ContactGroupCreateAttributes
object
2 properties
CommentCollection
object
1 property
ContactRelToMany
object
1 property
ContactCreateResource
object
3 properties
ContactResourceLinks
object
1 property
CommentReadResource
object
4 properties 2 required
CommentResource
object
Data related to a single comment
4 properties
ContactGroupCreateRepresentation
object
1 property
ContactRelData
object
2 properties
MessageRelToOne
object
2 properties
ContactGroupCollectionLinks
object
3 properties
ContactGroupCreateRelationships
object
1 property
ContactGroupRelationships
object
1 property
ContactGroupLinks
object
1 property
MessageRelLinks
object
2 properties
UserRelToOne
object
1 property
CommentCreateRepresentation
object
Request for contact comment creation
1 property
ContactGroupCollection
object
A collection of resources
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sedna-contact-api-api-openapi.yml Raw ↑

Other APIs SEDNA publishes across the network.

SEDNA Authentication API
AE Profile APIs.io
SEDNA Category Tag API API
AE Profile APIs.io
SEDNA Comment API API
AE Profile APIs.io
SEDNA Company API API
AE Profile APIs.io
SEDNA Document API API
AE Profile APIs.io
SEDNA Download API API
AE Profile APIs.io
SEDNA Event API API
AE Profile APIs.io
SEDNA Job Reference API API
AE Profile APIs.io
SEDNA Keyword API API
AE Profile APIs.io
SEDNA Message API API
AE Profile APIs.io
SEDNA Saved Search API API
AE Profile APIs.io
SEDNA Team API API
AE Profile APIs.io
#Contact API
← Back to S APIs
API Details
ID
sedna:sedna-contact-api-api
Base URL
https://example.sednanetwork.com/platform
Docs
https://developers.sedna.com/reference
Provider
SEDNA
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=sedna-contact-api-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/sedna-contact-api-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of SEDNA Contact API 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.