Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »

Paths

The format of all of the GET methods in this API are:

/MessageApi/<method>/<id>
or
/MessageApi/<method>/<id>?<variable>=<value>

The format of all of the POST methods in this API are:

/MessageApi/<method>Carrier Lookup Methods

URI

The uri endpoint invoked will be defined during client setup.  The method will be an HTTP POST with the entire body of the post consisting of the XML deliver content.

Client Response

Upon validating the request, the server shall respond with appropriate response code.  A successful message processed shall return an Http Server Response of 200.  If the server responds with an Http Server Response of anything other than 200, then there was a system error that occurred and the delivery will be attempted again.  Vibes will continue to attemp delivery of the message for the next 15 minutes before moving the message into an error queue and alerting Vibes Operations staff.  Once the problem has been resolved, the messages can be resent.

Note: The delivery recipient application must handle all message content delivered.  Messages that are considered invalid (ex: Bad keyword), are the responsibility of the client to log and acknowledge with Http Response 200, to keep Vibes delivery service from continually retrying delivery of the message.

Servers

Environment

Stability Level

Public Url

Server Host:port

UAT

Release Candidate

https://api.uat.vibesapps.com

catuat01.uat.vibes.com:8080 
catuat01.uat.vibes.com:8080

Production

Stable Production

https://api.vibesapps.com

connprod18.prod.vibes.com:8080 
connprod19.prod.vibes.com:8080 
dalpconapp05.dal.vibes.com:8080
dalpconapp06.dal.vibes.com:8080
dalpconapp07.dal.vibes.com:8080

  • No labels