dev.megaport.comMegaport API
dev.megaport.com Profile
dev.megaport.com
Maindomain:megaport.com
Title:Megaport API
Description:Security ¶ The following API endpoints are used for authentication Virtually every call requires a TOKEN that can be obtained following a successful login The UUID recorded in the “session” field is what you need to supply as the X-Auth-Token header for authentication of subsequent API calls All API calls are made over SSLTLS and every call is validated against the calling user
Discover dev.megaport.com website stats, rating, details and status online.Use our online tools to find owner and admin contact info. Find out where is server located.Read and write reviews or vote to improve it ranking. Check alliedvsaxis duplicates with related css, domain relations, most used words, social networks references. Go to regular site
dev.megaport.com Information
Website / Domain: |
dev.megaport.com |
HomePage size: | 641.491 KB |
Page Load Time: | 0.100006 Seconds |
Website IP Address: |
99.84.232.126 |
Isp Server: |
AT&T Internet Services |
dev.megaport.com Ip Information
Ip Country: |
United States |
City Name: |
Dallas |
Latitude: |
32.780879974365 |
Longitude: |
-96.80347442627 |
dev.megaport.com Keywords accounting
dev.megaport.com Httpheader
Content-Type: text/html |
Transfer-Encoding: chunked |
Connection: keep-alive |
Date: Thu, 20 Feb 2020 15:04:00 GMT |
Last-Modified: Mon, 10 Feb 2020 06:59:39 GMT |
Server: AmazonS3 |
Content-Encoding: gzip |
Vary: Accept-Encoding |
X-Cache: Hit from cloudfront |
Via: 1.1 1a6eb5e1dd6efbd323fd6d7c523cd1f3.cloudfront.net (CloudFront) |
X-Amz-Cf-Pop: SFO5-C1 |
X-Amz-Cf-Id: 6RyFx1tDksHj9Fg4WrhsX6_GhSQEovEKEW9axMkvkWe6iAEFzJKJlQ== |
Age: 10412 |
dev.megaport.com Meta Info
charset="utf-8"/ |
description="API documentation for Megaport. Megaport provides instantly provisioned, scalable bandwidth to public and private cloud endpoints, as well as between Data Centres as a Layer 2 VLAN."/ |
99.84.232.126 Domains
dev.megaport.com Similar Website
Domain |
WebSite Title |
dev.megaport.com | Megaport API |
onsitetraining.atlasapitraining.com | API Onsite Training for API 610, 570, 580, 653, 1169 - Atlas API Training |
megaport.com | Megaport | Cloud Interconnectivity Simplified |
api2.bigoven.com | 500,000+ Recipe and Grocery List API | BigOven API |
sms.cdyne.com | SMS API, As Low As $0.0015, #1 Text Message API, Short Code - CDYNE |
api.evdb.com | Events Feed, Concert & Event API - Eventful API |
api.eventful.com | Events Feed, Concert & Event API - Eventful API |
developer.yummly.com | Yummly | Recipe API & Food API |
developers.flipsnack.com | API documentation - Flipsnack API |
api.zeromq.org | ZeroMQ API - 0MQ Api |
docs.postmen.com | API Overview - Postmen - Postmen API Docs |
api.drupal.org | Drupal 8.8.x | API reference | Drupal API |
developer.active.com | ACTIVE Network API - The Active.com API |
developer.sportsengine.com | SportsEngine API |
api.corpwatch.org | CorpWatch API |
dev.megaport.com Traffic Sources Chart
dev.megaport.com Alexa Rank History Chart
dev.megaport.com Html To Plain Text
Back to top Overview Environments Run in Postman Security POST Login with User Details POST Login with Token GET Logout POST Change Password Lists Used for Ordering GET Locations GET Partner Megaports GET IX Locations Standard API Orders Price check in aisle three (overview) Ordering several services at once POST Validate Port Order Buy Port POST Buy Port POST Buy Ports in existing LAG POST Validate LAG Order POST Buy LAG POST Validate MCR2.0 Order POST Buy MCR2.0 POST Validate IX Order POST Buy IX POST Validate VXC Order POST Buy VXC Service Keys GET List Service Key POST Generate Service Key PUT Update Service Key Cloud Partner API Orders Who are the Cloud Partners? Smart port balancing POST Validate POST AWS - Buy POST AWS Hosted Connection - Buy GET Azure - step 1 - Lookup POST Azure - step 2 - Buy POST Alibaba - Buy GET Google - step 1 - Lookup POST Google - step 2 - Buy GET Nutanix - step 1 - Lookup POST Nutanix - step 2 - Buy GET Oracle - step 1 - Lookup POST Oracle - step 2 - Buy Price GET Port Price GET MCR2.0 Price GET New VXC Price GET New IX Price GET Speed Change Check Price GET Lifecycle Action Change Price Check Invoices GET All Invoices GET Single Invoice GET Single Invoice as PDF General GET Get Product List GET Get Product Details PUT Update PORT PUT Update MCR2.0 PUT Update VXC PUT Update IX POST Update Product Lifecycle Action Lock product to prevent editing POST Lock product DELETE Unlock product GET Check Interface Log Data GET Bandwidth Usage Read and write notification settings GET Read preferences PUT Write Preferences Documents GET Regenerate LOA for a service Service Metrics Data collection and processing Metric Types GET Get available metric types for Megaport products GET Get VXC telemetry data GET Get MEGAPORT telemetry data GET Get IX telemetry data GET Get MCR2.0 telemetry data The allows customers to interact with the business in the same way as the Megaport portal. All API call responses will include standard HTTP response codes: 200 - OK 400 - Bad request, typically caused by missing or incorrect request parameters 403 - Forbidden as you do not have sufficient permissions 500 - Server error, developers get emails directly from the App servers every time one of these occurs 503 - Server unavailable, down for maintenance A standard response to a request will include a message, plus optionally some data in the following schema: { âmessageâ: âSome message regarding the callâ, âdataâ: âAny data returned, in JSON formatâ } Environments ¶ There are two server environments that can be accessed using different URLs: https://api.megaport.com - this is the live production environment. You will be liable for any services ordered in this system. https://api-staging.megaport.com - this is a testing environment. You may perform any action in this system and the API calls and responses will be as per the production system but will not be deployed. It will also periodically be flushed and refreshed, and is expected to have lower availability requirements. Run in Postman ¶ Import the api collection into Postman by clicking the link below. Choose to create a new Collection. Once the collection is successfully ingested into Postman under Collections select Edit next to the imported Megaport collection. Select Variables , and add a key for âusernameâ and complete the value to be your Megaport.al username. Add another key for âpasswordâ and enter your Megaportal password. Then go to the Collection , and select Security -> Login with User Details and hit Send. The response json object will have a token key - copy this token. Then in the Collection, Edit, Variables section add another key for âtokenâ and paste the token into the corresponding value field. All the rest of the API calls should be ready to use. Security ¶ The following API endpoints are used for authentication. Virtually every call requires a TOKEN that can be obtained following a successful login. The UUID recorded in the âsessionâ field is what you need to supply as the X-Auth-Token header for authentication of subsequent API calls. All API calls are made over SSL/TLS, and every call is validated against the calling user account for appropriate permissions. We support two factor authentication by way of a Time-based One Time Password (TOTP) algorithm as defined by IETF RFC 6238 , and supported by the Google Authenticator mobile app on iOS and Android. Login with User Details ¶ POST /v2/login?username={username}&password={password}&oneTimePassword={oneTimePassword} Example URI POST /v2/login?username= username &password= password &oneTimePassword= oneTimePassword URI Parameters Hide Show username string (required) your username password string (required) your password oneTimePassword string (optional) a one time password as part of two factor authentication Response 200 Hide Show Headers Content-Type : application/json Body { " permissions ": { " 1544f278-ec03-11e5-9ce9-5e5517507c66 ": [ "financials" , "agent_create_employee" , "agent_create_sub_agency" , "tickets" , "approve_order" , "admin" , "services" , "tools" , "modify_service" , "create_employee" , "marketing" , "graphs" , "end_user" , "place_order" , "company_admin" , "create_sub_agency" , "virtual_employee" , "notifications" ] } , " sourceIp ": "103.252.15.1" , " username ": "admin" , " firstName ": "admin" , " lastName ": "admin" , " companyName ": "ADMIN" , " loginDate ": 1441066380875 , " expiryDate ": null , " locale ": null , " timeZone ": null , " session ": "1544f278-ec03-11e5-9ce9-5e5517507c66" , " language ": null , " userAgent ": null , " personId ": 2 , " personUid ": "1544f278-ec03-11e5-9ce9-5e5517507c66" , " companyId ": 1 , " companyUid ": "1544f278-ec03-11e5-9ce9-5e5517507c66" , " channelPartner ": null , " region ": null } Login with Token ¶ POST /v2/login/{token} Example URI POST /v2/login/ token URI Parameters Hide Show token UUID (required) valid session token Response 200 Hide Show Headers Content-Type : application/json Body { " permissions ": { " 1544f278-ec03-11e5-9ce9-5e5517507c66 ": [ "financials" , "agent_create_employee" , "agent_create_sub_agency" , "tickets" , "approve_order" , "admin" , "services" , "tools" , "modify_service" , "create_employee" , "marketing" , "graphs" , "end_user" , "place_order" , "company_admin" , "create_sub_agency" , "virtual_employee" , "notifications" ] } , " sourceIp ": "103.252.15.1" , " username ": "admin" , " firstName ": "admin" , " lastName ": "admin" , " companyName ": "ADMIN" , " loginDate ": 1441066380875 , " expiryDate ": null , " locale ": null , " timeZone ": null , " session ": "1544f278-ec03-11e5-9ce9-5e5517507c66" , " language ": null , " userAgent ": null , " personId ": 2 , " personUid ": "1544f278-ec03-11e5-9ce9-5e5517507c66" , " companyId ": 1 , " companyUid ": "1544f278-ec03-11e5-9ce9-5e5517507c66" , " channelPartner ": null , " region ": null } Logout ¶ GET /v2/logout/ Example URI GET /v2/logout/ Request Hide Show Headers X-Auth-Token : xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx Content-Type : application/json Response 200 Hide Show Headers Content-Type : application/json Change Password ¶ POST /v2/password/change?oldPassword={oldPassword}&newPassword={newPassword} Example URI POST /v2/password/change?oldPassword= oldPassword &newPassword= newPassword URI Parameters Hide Show oldPassword Text (required) current password newPassword Text (required) new password Request Hide Show Headers X-Auth-Token : xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx Content-Type : application/json Response 200 Hide Show Headers Content-Type : application/json Lists Used for Ordering ¶ For the majority of calls within the you will be operating upon ID values for various resources - things like data centre locations, Internet Exchange points etc. The following API calls detail the processes of obtaining lists of various items with relevance to the API functions. Locations ¶ The locations end point will return a list ...
dev.megaport.com Whois
"domain_name": [
"MEGAPORT.COM",
"megaport.com"
],
"registrar": "GoDaddy.com, LLC",
"whois_server": "whois.godaddy.com",
"referral_url": null,
"updated_date": [
"2020-07-14 11:24:29",
"2020-07-14 11:24:23"
],
"creation_date": "2002-07-14 00:16:43",
"expiration_date": "2021-07-14 00:16:43",
"name_servers": [
"NS-12.AWSDNS-01.COM",
"NS-1504.AWSDNS-60.ORG",
"NS-1839.AWSDNS-37.CO.UK",
"NS-693.AWSDNS-22.NET"
],
"status": [
"clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited",
"clientRenewProhibited https://icann.org/epp#clientRenewProhibited",
"clientTransferProhibited https://icann.org/epp#clientTransferProhibited",
"clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited",
"clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited",
"clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited",
"clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited",
"clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited"
],
"emails": "abuse@godaddy.com",
"dnssec": "unsigned",
"name": null,
"org": "Megaport (Services) Pty Ltd",
"address": null,
"city": null,
"state": "Queensland",
"zipcode": null,
"country": "AU"