REST APIs Sample Clauses

REST APIs. Table 9 – List of APIs for provisioning of virtual optical slices Table 10 – Create virtual optical slice specification Table 11 – Show virtual optical slice specification Table 14 – Delete virtual optical slice specification
Sample 1Sample 2
AutoNDA by SimpleDocs
REST APIs. Table 2 – List of APIs for provisioning of overlay virtual networks Table 3 – List networks specification Table 4 – Create network specification Table 5 – Bulk create networks specification Table 6 – Show network specification Table 7 – Update network specification Table 8 – Delete network specification
Sample 1Sample 2
REST APIs. Table 15 – List of APIs for provisioning of optical connectivity Table 16 – POST /restconf/config/optical-provisioning-manager:connection specification Table 17 – PUT /restconf/config/optical-provisioning-manager:connection/connectionID specification Table 18 – GET /restconf/config/optical-provisioning-manager:connection/connectionID specification
Sample 1
REST APIs. Table 21 – List of APIs for CRUD operations on forwarding rules Table 22 – POST /restconf/config/forwarding-rules-manager/connectionID Table 23 – PUT /restconf/config/forwarding-rules-manager /connectionID
Sample 1
REST APIs. Table 21 – List of APIs for the DCN information service Table 24 – POST /restconf/operations/opendaylight-port-statistics:get-node-connector-statistics specification 4.1 Successful response codes: 200 OK Error response codes: 400 BAD REQUEST, 403 FORBIDDEN, 404 NOT FOUND 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE POST /restconf/operations/opendaylight-flow-statistics:get-flow-statistics Request parameters NodeId String The unique identifier of the node. TableId String The unique identifier of the table. FlowId String The unique identifier of the flow. Response parameters Match Match object The classifier configured for the flow. Instruction List<Instruction object> The list of instruction configured for the flow. 1. Successful response codes: 200 OK Error response codes: 400 BAD REQUEST, 403 FORBIDDEN, 404 NOT FOUND 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE 4.1 Successful response codes: 200 OK Error response codes: 400 BAD REQUEST, 403 FORBIDDEN, 404 NOT FOUND 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE POST /restconf/operations/opendaylight-queue-statistics:get-all-queues-statistics-from-given-port Request parameters NodeId String The unique identifier of the node. PortId String The unique identifier of the port. Response parameters Queues List<Queue object> The list of the queues configured for the given port. Each Queue object includes: • Queue Id • QueueStats, as specified in the UML diagram in section 3.2.4.1 Successful response codes: 200 OK Error response codes: 400 BAD REQUEST, 403 FORBIDDEN, 404 NOT FOUND 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE
Sample 1
REST APIs. Table 29 – List of APIs for the DCN information service 1. Successful response codes: 200 OK Error response codes: 400 BAD REQUEST, 403 FORBIDDEN, 404 NOT FOUND 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE Request parameters NodeId String The unique identifier of the node. Response parameters Tables List<Table object> The list of the tables in a node. Each Table object includes: • Table Id • TableStats, as specified in the UML diagram in section 3.3.5.1 Successful response codes: 200 OK Error response codes: 400 BAD REQUEST, 403 FORBIDDEN, 404 NOT FOUND 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE Request NodeId String The unique identifier of the node. PortId String The unique identifier of the port. Response parameters Queues List<Queue object> The list of the queues configured for the given port. Each Queue object includes: • Queue Id • QueueStats, as specified in the UML diagram in section 3.3.5.1 Successful response codes: 200 OK Error response codes: 400 BAD REQUEST, 403 FORBIDDEN, 404 NOT FOUND 500 INTERNAL SERVER ERROR, 503 SERVICE UNAVAILABLE
Sample 1

Related to REST APIs

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Mark Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • Development Milestone Payments Pfizer shall make the payments set forth below within [**] days (or [**] days after [**] following the first occurrence of each event described below for a Licensed Product Covered by a Valid Claim that achieves such milestone (each event a “Development Milestone” and each payment a “Development Milestone Payment”). Development Milestone Development Milestone Payment [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**]. The Development Milestone Payment in clause (2) of this Section 3.3 may become payable as set forth in Section 4.6. Whether or not the Development Milestone in clause (2) of this Section 3.3 is achieved, the Development Milestone Payment in clause (2) shall, pursuant to Section 4.6, in all cases become payable prior to the time the Development Milestone Payment in clause (3) of this Section 3.3 becomes payable. With respect to the Development Milestone in clause (3) of this Section 3.3, in the case of a [**] that is determined to have become [**], such Development Milestone, if achieved based on such [**], shall be achieved upon [**]; provided, however, if either [**], such Development Milestone shall be deemed to have been met on the date of such determination. With respect to the Development Milestone in clause (8) of this Section 3.3, such Development Milestone will be paid in [**], provided that if such Licensed Product [**]. (For the avoidance of doubt, all payment [**] that became payable prior to such [**] shall continue to be payable and there shall be [**] of the [**] Development Milestone Payment will be deemed to have been achieved and payable on [**], and will be paid by Pfizer within [**] days thereafter, until the earlier of [**]. For example, [**] of such Development Milestone, such Development Milestone Payment would be paid [**] of the Development Milestone [**]. For the avoidance of doubt: (a) except for (i) the Development Milestone Payment set forth in clause (6) of this Section 3.3 [**], (ii) the Development Milestone Payment set forth in clause (8) of this Section 3.3 [**] and (iii) the Development Milestone Payment set forth in clause (9) of this Section 3.3 [**], each Development Milestone Payment shall be payable only once upon achievement of the applicable Development Milestone and only on the first occurrence of the corresponding Development Milestone regardless of the number of Licensed Products and (b) satisfaction of a Development Milestone by an Affiliate or by a sublicensee or assignee of, or Third Party retained by, Pfizer or its Affiliates shall be deemed to have been satisfied by Pfizer for the purposes of this Section 3.3.

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

  • License Agreement The Trust shall have the non-exclusive right to use the name "Invesco" to designate any current or future series of shares only so long as Invesco Advisers, Inc. serves as investment manager or adviser to the Trust with respect to such series of shares.

  • Final Design Provide OWNER with proposed final construction drawings and detailed opinions of probable total Project construction costs in writing for OWNER' s review, prior to completion of the final Contract Documents, so that any changes that may be necessary in accordance with Project' s budgetary schedule can be made prior to bid.

  • Research License Each Collaborator shall allow the other Collaborator to practice any of its Non- Subject Inventions for the purpose of performing the Cooperative Work. No license, express or implied, for commercial application(s) is granted to either Collaborator in Non-Subject Inventions by performing the Cooperative Work. For commercial application(s) of Non-Subject Inventions, a license must be obtained from the owner.

  • Development Costs Licensee shall be responsible for all of its costs and expenses in connection with the Development of, and obtaining and maintaining Regulatory Approvals for, the Licensed Products in the Field in the Territory.

  • Milestone Payment The first time Net Sales in the Territory in a Royalty Period exceed US$[***] ([***] dollars) US$[***] ([***] dollars)

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!