Developer & APIs

Has anyone been able to successfully integrate EMG notifications with google's pub/sub? I have been at this for months and am not successful.Basic path is:EMG event such as port down is triggeredThis event, which is picked up by the python outgoing notifications script located at https://github.com/equinix/messaging-gateway-templates/tree/master/template-python-outgoing-notifications-v1, which I have deployed as a cloud function and scheduled to run every 2 minutes, is then sent to pub/subthe pub/sub notification is sent out as an email notification to my team.Is anyone able to assist?

I use shipment v2 API in playground.URL of my request: https://playgroundapi.equinix.com/colocations/v2/orders/shipmentsJSON data of my request: { "type": "INBOUND", "requestedDateTime": "2023-03-02T10:45:41Z", "cageId": "1234", "details": { "carrier": "OTHER", "carrierName": "New Carrier", "numberOfBoxes": 2, "carrierTrackingNumbers": [ "t1Z294AK92654678989", "t1Z086DK96424456780" ] } } I get two possible responses for this same request:504 gateway time-out error { "fault": { "faultstring": "Gateway Timeout", "detail": { "errorcode": "messaging.adaptors.http.flow.GatewayTimeout" } } } 204 No ContentHowever according to API docs, I should get 201 and the order id.

I am passing JSON for ordering outbound shipments. The JSON is below but its pretty much that same as my inbound JSON which is fine. The issue I am getting with the outbound order is that I am getting this error:   b'[{"errorCode":"EQ-2016010","errorMessage":"One or more properties are invalid","correlationId":"105073684364570","additionalInfo":[{"property":"details.carrierTrackingNumbers","reason":"details.carrierTrackingNumbers should NOT have more than 1 items","value":["123456789", "987654321"]}]}]' My JSON: { "type": "OUTBOUND", "customerReferenceId": "x", "requestedDateTime": "2023-04-12T07:00:00.000Z", "cageId": "x", "details": { "carrier": "FEDEX", "numberOfBoxes": 2, "declaredValue": 1, "declaredValueCurrency": "USD", "carrierTrackingNumbers": [ "123456789", "987654321" ], "shipmentLabelRequired": false } } Just for reference this is my inbound which is working as expe

This is the first release of the Equinix Ansible Collection. This collection will mature to succeed the Ansible Equinix Metal collection.  The big difference with this collection is that the goal of the project is to cover all Equinix APIs over time, starting with Metal, Fabric, and Network Edge.   If you are just getting started with Ansible on Equinix, this is the project to use. Let us know which features you’ll need for your playbooks. We’ve stubbed out issues for all of the resources that will be needed to put this provider on parity with the Equinix Terraform provider which has the the most complete IaC coverage today.   Broader API coverage is being facilitated by the move away from legacy, hand-crafted, Python SDKs (packet-python).  We will favor (and produce) SDKs generated from the OpenAPI spec for each Equinix API that will be supported. Metal Python is the first of these, an SDK built for wide adoption. Its readiness to simplify the A

The 0.2.0 release of pulumi-equinix includes Pulumi SDKs generated with v1.14.1 of terraform-provider-equinix. This release includes a bug fix that improve usability of single-element set- and list-type fields; deprecation notices for facility-related fields to prepare for the deprecation of facilities in the Equinix Metal platform; and support for key types in Network Edge SSH key resources, which makes it possible to provision Arista routers in Network Edge with Pulumi.

The 1.14.0 release of terraform-provider-equinix includes code and documentation to help users identify and update Terraform configurations that are impacted by the deprecation of facilities in the Equinix Metal platform. In addition, this release adds support for the DSA key type in the equinix_network_ssh_key resource, which makes it possible to provision routers in Network Edge with Terraform.

Hello, I have a question. ## Question.Is there a best practice to get all CIRCUIT,SENSOR data? ## BackgroundWe are developing and operating a monitoring system for current and temperature sensors in a Datacenter. We would like to import data from Smartview into our monitoring system and are considering using the API. We need data for each CIRCUIT and SENSOR, but if we use the following API, we can only get summary data for the specified unit. === e.g. Current (Power_v1) request ❯ curl --request GET \ --url 'https://api.equinix.com/power/v1/current?accountNo={accountNo}&ibx={ibx}&levelType=ibx&levelValue={ibx}' \ --header 'accept: application/json' \ --header 'authorization: Bearer {bearer}' \ --header 'content-type: application/json' Next, we considered how to obtain a list of CIRCUIT,SENSOR from the HierarchyAPI and request one of each. However, we found that the API limits the number of requests to 1,000 per day. We have more than 1,000 CIRCUITs and SENSORs that we want t

I am trying to generate token using this method but in Postman: Access Token using grant_type = client_credentials (Recommended). POST 'https://api.equinix.com/oauth2/v1/token' -H "content-type: application/json" -d '{ "grant_type": "client_credentials", "client_id": "******", "client_secret": "****" }' I have the body set as specified in the link: https://developer.equinix.com/docs?page=/dev-docs/fabric/overview but when I execute the query I get this error: { "errorDomain": "apps-fqa", "errorTitle": "Unable to Process the Request", "errorCode": "S1002", "developerMessage": "Failed to execute the ExtractVariables: extractjsonparams", "errorMessage": "Unable to Process the Request, Please try again later." } I have a client_id and client_sercret generated and have tested it with Terraform. What am I missing?Thanks!

This is the first release of the pulumi-equinix collection, a successor to the pulumi-metal collection. The new release includes Pulumi generated SDKs for various languages (.NET, Python, TypeScript, Java, and Go) that cover not only Metal, but also Network Edge, and Fabric resources. 

This is the first release of metal-python, a generated Python SDK for the Equinix Metal API and successor to our original packet-python. By taking advantage of the OpenAPI spec for the Metal API, this SDK offers far greater API coverage. Advantages over packet-python include support for Metal Gateway, VRF, Interconnection, and more. The Metal Python SDK has already been put to use, backing the new Metal modules in the Ansible Collection for Equinix (ansible-collection-equinix).

Equinix Internet Access is now on the Equinix Developer platform.  Catalog | Developer Platform (equinix.com)

This release is v3.6.0 of the cloud-provider-equinix-metal project, which provides a Kubernetes cloud controller manager for Equinix Metal. It includes 25 changes, the most exciting change being an upgrade path for users to get the latest version of MetalLB. This means better BGP-based network load balancing across their enabled worker nodes via custom resources. A lesser but still important change is that CPEM no longer does a health check on an incorrect service if said service was created in the default namespace. Various other updates were also bundled into this version such as updating Go language dependencies and improving linting for developer code. Check out the CPEM documentation for MetalLB for more details and review a sample migration path provided by MetalLB.

This release of our experimental generated Go SDK for the Equinix Metal API adds support for additionalProperties as required in the OpenAPI v3 specification.  The new support for additionalProperties allows Go SDK clients to access properties that are included in API responses but are not documented in the API spec and improves the compatibility of the generated Go SDK with future API releases.  This release also introduces a default User-Agent header for improved usage metrics.  Finally, this helps transition us from the old Packet packngo SDK! To learn more about our generated Go SDK, visit the equinix-labs/metal-go repo on GitHub.

I am able to successfully create a connection to "AWS Direct Connect" via the APIs. However, the docs recommends in step 5: 5. Validate your AWS Account ID Use the Validate Connection Authorization Key API request to verify that your AWS Account ID can be used to create a connection to the selected service profile in the given metro. Doing a POST to /fabric/v4/connections/validate   { "filter": { "and": [ { "property": "/zSide/accessPoint/authenticationKey", "operator": "=", "values": [ "123456789" ] }, { "property": "/zSide/accessPoint/profile/uuid", "operator": "=", "values": [ "69ee618d-be52-468d-bc99-00566f2dd2b9" ] } ] } }   and it always returns a 400 Bad Request   [ { "errorCode": "EQ-3142601", "errorMes

When setting up an Azure ExpressRoute, how is the redundant connection configured? Do I create 2 separate connections, and have one be redundant.priority PRIMARY, and the other SECONDARY? What's the difference between the "redundancy" in the connection, and the "redundancy" under the aside/zside port configuration?

Missed the livestream? Here's your chance to explore Cluster APIs with Fen Aldrich and Chris Privitere from the Equinix DevRel Development Team. 

Hello,I would like to create a L2 connection in the sandbox but I'm having some problems. I can get a list of ports but I can't get a service profile using GET /fabric/v4/serviceProfiles. When I try to create a service profile I get the message "PENDING APPROVAL" but I can't find a way to approve this service profile.What would be the best way to test the setup of L2 connections to Azure, AWS and Google in the the sadbox environment?Any help is appreciated.Thanks

Hi, I am using the API to open inbound orders and I received a call today that the Shipping team cannot scan the tracking numbers and associate them to a ticket. It looks like the API is putting the tracking number string into a list instead of a string which is causing this,   ['626467467487', '626467467454', '626467467465', '626467467476']. I have my app posting this in a string format using the catalog on the developer portal. The portal does state that the tracking numbers need to be inside brackets so could that be the reason?   "carrierTrackingNumbers": [  "DHL930182000"], That is the example from the catalog, I believe the brackets are causing the issue here with the Shipping department at the site.

I'm trying to create a primary and secondary GCP connection. I created a primary connection, however, when I try to create the secondary connection I get the following response: [ { "errorCode": "EQ-3142303", "errorMessage": "Only Primary connection allowed for this CSP", "details": "Given service profile does not allowed redundant connection", "correlationId": "null-0000-103912200151-api", "additionalInfo": [ { "property": "/redundancy/priority" } ] } ] However, if I get the service profile details via the API: https://api.equinix.com/fabric/v4/serviceProfiles/{UUID} in the "metadata" section there is an attribute "redundantProfileId" which lists the profile Id I was using to try and create a redundant connection. Am I misunderstanding this as it seems that since there is a "redundantProfileId" listed that the profile should support redundant connections?

For example, if I want to use Equinix Fabric to set up and operate AWS, is it possible to use the EquinixFabric API for management within AWS (EC2 startup, life-and-death monitoring, etc.)? Or is it necessary to use APIs provided by AWS?When using multiple Azure and GCP, it is a concern to use the API provided by each.Thank you.

Hi Community, I wanted to start a chat around some dev ops tools that we know many of our customers use. I'll throw a few questions below to get us started but feel free to go off topic if you want to discuss something outside of these questions. Does your organization use Ansible, Terraform, or both? Are there other automation tools that you use or prefer? What do you like/dislike about each of these tools? How can we improve the user experience when using these tools with Platform Equinix?

Hi, I have a circuit and I'm trying to change the bandwidth using PATCH /fabric/v4/connections/{id} Here's the payload: { "op": "replace", "path": "/bandwidth", "value": 900} But I keep getting this error code and there seems to be no way around it. [ { "errorCode": "EQ-3142506", "errorMessage": "Invalid request", "details": "Media type is not supported", "correlationId": "X-X-X-api" }] Would appreciate the help, Thanks

I created the following query filter to use with the https://api.equinix.com/fabric/v4/connections/search API to retrieve all "non-deprovisioned" connections: { "filter": { "AND": [ { "property": "/operation/equinixStatus", "operator": "=", "values": [ "PENDING_APPROVAL", "PROVISIONING", "PROVISIONED", "NOT_PROVISIONED", "REJECTED", "PENDING_BGP_PEERING" ] }, { "property": "/aSide/accessPoint/location/metroCode", "operator": "=", "values": [ "SV" ] } ] }, "pagination": { "limit": 3000, "offset": 0 }, "sort": [ { "property": "/name", "direction": "DESC" } ] } The results of the abov

How can I access utilization data for a Virtual Circuit connection using the APIs?

I sent a request to setup a primary and secondary connection with the body containing data structured like the following: { "data": [ { "type": "EVPL_VC" }, { "type": "EVPL_VC" } ] } When sending this I get the following error response which is obviously not correct: [ { "errorCode": "EQ-3142501", "errorMessage": "Invalid argument value passed", "details": "Invalid request type", "correlationId": "null-0000-103911409258-api", "additionalInfo": [ { "property": "/type", "reason": "Allowed values: EVPL_VC, EPL_VC, IP_VC, ACCESS_EPL_VC" } ] } ] The type field in both cases is set to a valid value, EVPL_VC. If I just create a single connection with either of the entries of the data array the connections setup properly.