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 13 contracts
Samples: Cooperative Purchasing Master Contract, Master Services and Purchasing 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;
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 11 contracts
Samples: 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 5 contracts
Samples: Justice Services Agreement, 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 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
Samples: 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. 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