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
Everbridge

Everbridge Expected Locations API

EB Suites - Expected Location Management

Documentation Provider Profile APIs.io OpenAPI GitHub

Everbridge Expected Locations API is one of 91 APIs that Everbridge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Expected Locations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 7 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.everbridge.net/rest, https://api.everbridge.eu/rest.

7 operations 4 paths 11 schemas 2 DELETE2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.everbridge.net/rest
Authentication
API Key, HTTP Basic, API Key
Resource Areas
1

Authentication & Security 3

Everbridge Expected Locations API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (API_Authorizer). It accepts HTTP basic authentication (BasicAuth). An API key is passed in the header as x-api-key (api_key).

  • API_Authorizer — oAuth Token
  • BasicAuth — Basic Authentication Token
  • api_key — API Key - For System Use

Paths & Operations 7

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

Expected Locations 7

EB Suites - Expected Location Management

POST
/expectedLocations/{organizationId}
Add Expected Locations
EBS Add Expected Locations 3 params body → 200400401404500
DELETE
/expectedLocations/{organizationId}/batch
Delete Batch
EBS Delete Batch Expected Locations 1 param body → 200400401404500
GET
/expectedLocations/{organizationId}/{contactId}
List Expected Location For Contact
EBS List Expected Location For Contact 3 params → 200400401404500
POST
/expectedLocations/{organizationId}/{contactId}
Create Expected Location For Contact
EBS Create Expected Location For Contact 3 params body → 200400401404500
DELETE
/expectedLocations/{organizationId}/{contactId}/{expectedLocationId}
Delete Expected Location For Contact
EBS Delete Expected Location For Contact 4 params → 200400401404500
GET
/expectedLocations/{organizationId}/{contactId}/{expectedLocationId}
Get Expected Location For Contact
EBS Get Expected Location For Contact 4 params → 200400401404500
PUT
/expectedLocations/{organizationId}/{contactId}/{expectedLocationId}
Update Expected Location For Contact
EBS Update Expected Location For Contact 4 params body → 200400401404500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are ContactAddressWrapper (17 properties), ContactAddressInstance (17 properties), ExpectedLocationWrapper (15 properties), ExpectedLocationInstance (8 properties). Each schema is shown below with its type and property counts.

RestfulInstanceResult
object
2 properties
RestfulModificationResult
object
4 properties
RestfulBatchOperationResult
object
3 properties
GisLocationWrapper
object
2 properties
ContactAddressWrapper
object
17 properties 5 required
organizationId
integer
Everbridge Organization id. Available on manager portal (Settings -- Organization -- Base Information)
ExpectedLocationInstance
object
8 properties
ExpectedLocationInstanceResult
object
2 properties
ContactAddressInstance
object
17 properties
ExpectedLocationWrapper
object
15 properties 1 required
ExpectedLocationCollectionResult
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

everbridge-expected-locations-api-openapi.yml Raw ↑

Other APIs Everbridge publishes across the network.

Everbridge iPaaS API
AE Profile APIs.io
Everbridge Asset Association Definition API
AE Profile APIs.io
Everbridge Asset License Limit Stats API
AE Profile APIs.io
Everbridge Asset Type Templates API
AE Profile APIs.io
Everbridge Asset Types API
AE Profile APIs.io
Everbridge Asset Upload Batches API
AE Profile APIs.io
Everbridge Assets API
AE Profile APIs.io
Everbridge Assets Batch API
AE Profile APIs.io
Everbridge Assets Query API
AE Profile APIs.io
Everbridge Attachments API
AE Profile APIs.io
Everbridge Audio API
AE Profile APIs.io
Everbridge Audit Log API
AE Profile APIs.io
#Expected Locations
← Back to E APIs
API Details
ID
everbridge:everbridge-expected-locations-api
Base URL
https://api.everbridge.net/rest
Docs
https://developers.everbridge.net/home/reference
Provider
Everbridge
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=everbridge-expected-locations-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/everbridge-expected-locations-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 Everbridge Expected Locations 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.