IP Library Granted Patent US 9,351,134
Granted Patent B2
US 9,351,134 · App. 14/474,101 · Granted May 24, 2016

Messaging service application programming interface

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,351,134
App. No.
14/474,101
Granted
May 24, 2016
Kind
B2
Abstract

A system comprising a computer-readable storage medium storing at least one program and a computer-implemented method that enables short message service (SMS) text messaging to be integrated into existing applications is presented. Consistent with some embodiments, the method may include receiving a request from a client application to transmit a message to a recipient device. The method may further include validating the request to ensure that the telephone number is valid and that the message conforms to a predefined messaging standard. In response to successfully validating the request, the method causes transmission of the message to the recipient device.

Claims (42)

1. A system comprising:

an application programming interface server configured to receive, from a client application executing on a client device, a message transmission request, the message transmission request including a plurality of parameters, the plurality of parameters specifying a telephone number assigned to a recipient device and a message for transmission to the recipient device;

an inbound module, comprising one or more processors of a machine, configured to determine that the message transmission request is valid, the inbound module to determine that the message transmission request is valid by performing operations including determining that the telephone number is valid and determining that the message conforms to a predefined messaging standard;

the inbound module further configured to add the message transmission request to an outbound queue based on determining the message transmission request is valid;

an outbound module configured to:

cause transmission of the message to the recipient device based on the message transmission request being included in the outbound queue;

obtain status information specifying a status of transmission of the message, the status information including an indication of successful transmission of the message; and

add the message transmission request and the status information to a reporting queue; and

a reporting module configured to store a record of the message transmission request based on the message transmission request and the status information being added to the reporting queue, the record including the message and the indication of successful transmission of the message.

2. The system of claim 1 , further comprising a reporting module configured to store a record of the message transmission request in a machine-readable medium responsive to the outbound module causing the transmission of the message.

3. The system of claim 1 , wherein the inbound module determines the telephone number is valid by determining that the telephone number includes a particular number of digits.

4. The system of claim 1 , wherein the outbound module causes the message to be transmitted to the recipient device by performing operations including transmitting a request to a Short Message Service (SMS) aggregator, the request identifying the telephone number and a telephone carrier associated with the recipient device, the SMS aggregator to route the message to the telephone carrier.

5. The system of claim 1 , wherein the predefined messaging standard specifies a particular format for the message.

6. The system of claim 1 , wherein the message is transmitted as a Short Message Service (SMS) message.

7. The system of claim 1 , wherein the message transmission request is a Hypertext Transfer Protocol (HTTP) request.

8. A method comprising:

receiving, from a client application executing on a client device, a message transmission request, the message transmission request including a plurality of parameters, the plurality of parameters specifying a telephone number assigned to a recipient device and a message to transmit to the recipient device;

determining that the message transmission request is valid, the determining that the message transmission request is valid including determining that the telephone number is valid and determining that the message conforms to a predefined messaging standard;

adding the message transmission request to an outbound queue based on determining the message transmission is valid;

causing transmission of the message to the recipient device based on the message transmission request being included in the outbound queue;

obtaining status information specifying a status of transmission of the message, the status information including an indication of successful transmission of the message;

adding the message transmission request and the status information to a reporting queue; and

storing a record of the message transmission request based on the message transmission request and the status information being added to the reporting queue, the record including the message and the indication of successful transmission of the message.

9. The method of claim 8 , further comprising authenticating a client associated with the client application, wherein the authenticating of the client includes verifying a user name and password associated with the client.

10. The method of claim 8 , further comprising verifying that a user of the recipient device has approved of receiving messages from the client application.

11. The method of claim 8 , further comprising identifying a telephone carrier associated with the telephone number.

12. The method of claim 11 , wherein the causing of the transmission of the message to the recipient device includes transmitting a request to an SMS aggregator, the request including the message, telephone number, and the telephone carrier, wherein the SMS aggregator routes the message to the telephone carrier and the telephone carrier routes the message to the recipient device.

13. The method of claim 8 , wherein the determining that the telephone number is valid is based on the telephone number including a particular number of digits.

14. The method of claim 8 , further comprising storing a record of the transmission of the message to the recipient device.

15. The method of claim 8 , further comprising adding the message transmission request to the outbound queue.

16. The method of claim 14 , further comprising transmitting the record of the transmission of the message to a client associated with the client application.

17. The method of claim 8 , wherein the message transmission request is based on a Hypertext Transfer Protocol (HTTP) format.

18. The method of claim 8 , wherein the message is transmitted as a Short Message Service (SMS) message.

19. The method of claim 8 , wherein the predefined messaging standard prohibits use of profanity.

20. A non-transitory machine-readable storage medium embodying instructions that, when executed by a machine, cause the machine to perform operations comprising:

receiving, from a client application executing on a client device, a message transmission request, the message transmission request including a plurality of parameters, the plurality of parameters specifying a telephone number assigned to a recipient device and a message to transmit to the recipient device;

determining that the message transmission request is valid, the determining that the message transmission request is valid including determining that the telephone number is valid and determining that the message conforms to a predefined messaging standard;

adding the message transmission request to an outbound queue based on determining the message transmission is valid;

causing transmission of the message to the recipient device based on the message transmission request being included in the outbound queue;

obtaining status information specifying a status of transmission of the message, the status information including an indication of successful transmission of the message;

adding the message transmission request and the status information to a reporting queue; and

storing a record of the message transmission request based on the message transmission request and the status information being added to the reporting queue, the record including the message and the indication of successful transmission of the message.

Assignments (15)
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Recorded Aug 30, 2024
From: ZETA GLOBAL CORP.; ZSTREAM ACQUISITION LLC
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 068822/0154 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT REEL 055212, FRAME 0964 Recorded Aug 30, 2024
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: ZETA GLOBAL CORP.
Reel/Frame 068822/0167 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 15, 2024
From: 935 KOP ASSOCIATES, LLC
To: ZETA INTERACTIVE CORP.
Reel/Frame 066471/0267 →
RELEASE OF SECURITY INTEREST Recorded Mar 2, 2021
From: PNC BANK, NATIONAL ASSOCIATION
To: ZETA GLOBAL CORP.
Reel/Frame 055458/0084 →
RELEASE OF SECURITY INTEREST Recorded Feb 11, 2021
From: FIRST EAGLE PRIVATE CREDIT, LLC, AS SUCCESSOR TO NEWSTAR FINANCIAL, INC
To: ZBT ACQUISITION CORP.; ZETA GLOBAL CORP.; 935 KOP ASSOCIATES, LLC
Reel/Frame 055282/0276 →
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Recorded Feb 3, 2021
From: ZETA GLOBAL CORP.
To: BANK OF AMERICA, N.A.
Reel/Frame 055212/0964 →
SECURITY INTEREST Recorded Dec 3, 2020
From: ZETA GLOBAL CORP.
To: FIRST EAGLE PRIVATE CREDIT, LLC
Reel/Frame 054585/0770 →
SECURITY INTEREST Recorded Jul 24, 2017
From: ZETA INTERACTIVE CORP.; ZETA INTERACTIVE, LLC; SPIREVISION HOLDINGS, INC.; ORIGIN INTERACTIVE GROUP, LLC; LEVELOCITY, LLC
To: PNC BANK, NATIONAL ASSOCIATION
Reel/Frame 043073/0210 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PCT APPLICATION NUMBER PCT/2014/054348 PREVIOUSLY RECORDED AT REEL: 042272 FRAME: 0069. ASSIGNOR(S) HEREBY CONFIRMS THE CHANGE OF NAME. Recorded May 9, 2017
From: ZETA INTERACTIVE CORP.
To: ZETA GLOBAL CORP.
Reel/Frame 042430/0291 →
CHANGE OF NAME Recorded May 8, 2017
From: ZETA INTERACTIVE CORP.
To: ZETA GLOBAL CORP.
Reel/Frame 042272/0069 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 20, 2016
From: EBAY INC.
To: 935 KOP ASSOCIATES, LLC
Reel/Frame 038953/0250 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 20, 2016
From: RUTTENBUR, ERIC P.
To: EBAY INC.
Reel/Frame 038953/0209 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 7, 2016
From: EBAY, INC.
To: 935 KOP ASSOCIATES, LLC
Reel/Frame 037431/0910 →
SECURITY INTEREST Recorded Nov 3, 2015
From: 935 KOP ASSOCIATES, LLC
To: NEWSTAR FINANCIAL, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 036949/0748 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 3, 2014
From: RUTTENBUR, ERIC P.
To: EBAY INC.
Reel/Frame 033655/0015 →