Go SDK | Inside Equinix Developer Tech
In this video, David Flanagan, a.k.a. Rawkode, does a deep dive on the Equinix GO SDK. David explores how to leverage webhooks and APIs with the Equinix SDK to build pipelines for remediation, automation, and notifications. We'll demonstrate how to send GET requests, showing the requests made and their results. This approach allows for dynamic capacity checks based on environment variables, integrated seamlessly with your infrastructure. This was a brief yet insightful introduction to the Equinix SDK. Go ahead, experiment with the Equinix SDK, and share your creations with us. Until next time, have a great day!93Views0likes0CommentsMeet the Product Managers!
Hello Equinix Community, I'm Jantzen Belliston, Sr Manager at Equinix. Today, we're opening a new chapter in our commitment to fostering transparency and community by introducing you to the incredible individuals behind our innovative products. The essence of Equinix has always been a blend of technology and community. We understand that the pulse of any tech-driven organization is its products, and behind those products, there's a team of dedicated, passionate individuals: our Product Managers. This thread offers a unique opportunity for our customers to get to know these dedicated professionals on a personal level. Our product team is thrilled to be a part of this platform, as it offers us a direct channel to engage, share, and grow with all of you. We see the Equinix Community not just as a space for interactions, but as a bridge to understand your needs, address your questions, and co-create the future. Here’s what to anticipate: Personal Introductions: Our Product Managers from various domains will be stepping forward to share about themselves, their roles, and the inspirations behind the products they steer. Behind-the-Scenes Stories: Insights into the ideation, challenges, and milestones of our product journeys – straight from those who live and breathe them. Open Dialogue: We're building a two-way street. Engage directly with our product teams, share your feedback, or ask anything you've ever wondered about our offerings. Sharing Expertise: Expect enlightening discussions, from technological deep dives to evolving market trends, all from the experts behind our product lineup. I invite our vibrant community to dive into these conversations, ask questions, and truly get to know the people who shape the products and services you trust. Warm regards, Jantzen12KViews6likes9CommentsRedesigned Developer Settings | Developer Platform
We have recently launched a for accessing your developer settings such as App Management and EMG subscriptions. With the improved UI, you can: Access your developer settings via Equinix portal and discover our product and services using a single unified login. Easily and efficiently manage your Equinix apps and subscriptions (including the ability to search, filter and sort) When logging in, you will be redirected to Equinix Customer Portal where you can sign in using your email login credentials. To access the app dashboard or EMG subscription, use the left navigation and select Developer Settings. There is no impact to existing apps and subscriptions and your integration will continue to work.62Views0likes0CommentsSmart Hands ticket api
Hello guys, I am new in using curl and I have a qeustion. How it looks the final example autharization form + get smart hands type. curl -XPOST 'https://api.equinix.com/oauth2/v1/token' -H "content-type: application/json" -d '{ "grant_type": "client_credentials", "client_id": "ABCDE12345", "client_secret": "FGHIJ67890" }' and curl -X GET "https://api.equinix.com/v1/orders/smarthands/types" -H "content-type: application/json" -H "authorization: Bearer qwErtYxxxxxxxcdefGHI" I don't understand how to combine these two example in one and why I have to use second time -H "authorization: Bearer qwErtY8zyW1abcdefGHI"Solved1.9KViews0likes1CommentPermissons Issue
I recevved the above error while trying to add a workvisit request. I'm doing some integration testing and trying to perform some negative tests so my software is able to report failures accurately. The error in itself is not really very informative so if anyone else who has seen this knows the cause I'd love to know! { "errors": [ { "code": "EQX-161-403", "message": "Insufficient permission to access the resource or invoke the request." } ], "ticketId": "190806075245093" }6.2KViews0likes9CommentsUnable to filter using "dateRange" for OrderHistory_v1
When filtering with dateRange on the OrderHistory_v1 API i get a statusCode 400 returned. Other filters work fine for me and return expected results I am using the following payload { "filters": { "dateRange": [ "PAST_7_DAYS" ] } } The errors I receive are: code: "EQX-171-1212" path: "/filters/dateRange" message: "instance value (%s) not found in enum (possible values: %s) PAST_7_DAYS" Thank you in advance2KViews0likes1Comment