Common use of API Content Clause in Contracts

API Content. All content related to API Service, other than Customer Content or Customer’s API Client content, is considered Axon’s API Content, including: 5.1. the design, structure and naming of API Service fields in all responses and requests; 5.2. the resources available within API Service for which Customer takes actions on, such as evidence, cases, users, or reports; 5.3. the structure of and relationship of API Service resources; and 5.4. the design of API Service, in any part or as a whole.

Appears in 18 contracts

Sources: Professional Services Contract, Master Services and Purchasing Agreement, Cooperative Purchasing Master Contract

API Content. All content related to API Service, other than Customer Agency Content or CustomerAgency’s API Client content, is considered Axon’s API Content, including: 5.1. the design, structure and naming of API Service fields in all responses and requests; 5.2. the resources available within API Service for which Customer Agency takes actions on, such as evidence, cases, users, or reports; 5.3. the structure of and relationship of API Service resources; and 5.4. the design of API Service, in any part or as a whole.

Appears in 13 contracts

Sources: Contract, Axon Evidence Justice Services Agreement, Master Services and Purchasing Agreement

API Content. All content related to API Service, other than Customer Agency Content or CustomerAgency’s API Client content, is considered Axon’s API Content, including: 5.1. the design, structure and naming of API Service fields in all responses and requests; 5.2. the resources available within API Service for which Customer Agency takes actions on, such as evidence, cases, users, or reports;; and 5.3. the structure of and relationship of API Service resources; and 5.4. the design of API Service, in any part or as a whole.

Appears in 6 contracts

Sources: Master Services and Purchasing Agreement, Justice Services Agreement, Master Services and Purchasing Agreement

API Content. All content related to API Service, other than Customer Content or Customer’s API Client content, is considered Axon’s API Content, including: : 5.1. the design, structure and naming of API Service fields in all responses and requests; 5.2. the resources available within API Service for which Customer takes actions on, such as evidence, cases, users, or reports; 5.3. the structure of and relationship of API Service resources; and 5.4. the design of API Service, in any part or as a whole.

Appears in 2 contracts

Sources: Addendum to Agreement, Addendum to Agreement

API Content. All content related to API Service, other than Customer Content or Customer’s API Client content, is considered Axon’s API Content, including: 5.1. : the design, structure and naming of API Service fields in all responses and requests; 5.2. ; the resources available within API Service for which Customer takes actions on, such as evidence, cases, users, or reports; 5.3. ; the structure of and relationship of API Service resources; and 5.4. and the design of API Service, in any part or as a whole.

Appears in 2 contracts

Sources: Master Services and Purchasing Agreement, Master Services and Purchasing Agreement

API Content. All content related to API Service, other than Customer Content or Customer’s 's API Client content, is considered Axon’s 's API Content, including: 5.1. the design, structure and naming of API Service fields in all responses and requests; 5.2. the resources available within API Service for which Customer takes actions on, such as evidence, cases, users, or reports; 5.3. the structure of and relationship of API Service resources; and 5.4. the design of API Service, in any part or as a whole.

Appears in 1 contract

Sources: First Amendment to the Axon Agreement

API Content. All content related to API Service, other than Customer Content or Customer’s API Client content, is considered Axon’s API Content, including: 5.1. a) the design, structure and naming of API Service fields in all responses and requests; 5.2. b) the resources available within API Service for which Customer takes actions on, such as evidence, cases, users, or reports; 5.3. c) the structure of and relationship of API Service resources; and 5.4. d) the design of API Service, in any part or as a whole.

Appears in 1 contract

Sources: Master Services and Purchasing Agreement

API Content. All content related to API Service, other than Customer Agency Content or Customer’s Agency’s API Client content, is considered Axon’s Axon’s API Content, including: 5.1. the design, structure and naming of API Service fields in all responses and requests; 5.2. the resources available within API Service for which Customer Agency takes actions on, such as evidence, cases, users, or reports; 5.3. the structure of and relationship of API Service resources; and 5.4. the design of API Service, in any part or as a whole.

Appears in 1 contract

Sources: Master Services and Purchasing Agreement