Skip to main content
Every payload includes a top-level eventType field with the name of the event, so an endpoint subscribed to several events can tell them apart:
We may add new fields to payloads over time. Ignore fields you don’t use instead of rejecting payloads that contain them.

proposal.accepted

Occurs whenever the customer accepts a proposal on Upwork.
Request data sample

chat.message.sent

Occurs whenever the customer sends you a new message in a conversation.
Request data sample

bid_intent.scheduled

Occurs whenever Auto-Bidder schedules a bid.
Request data sample

job.matched

Occurs whenever a new Upwork job matches one of your scanners.
Request data sample

bid_intent.submitted

Occurs whenever Auto-Bidder submits a proposal on Upwork.
Request data sample

proposal.new_result

Occurs whenever a sent proposal gets a new status, for example when the client views it or replies. proposal.status is one of:
Request data sample

invite.new

Occurs whenever one of your freelancers receives a job invite on Upwork.
Request data sample

direct_message.new

Occurs whenever a client writes to one of your freelancers directly, in a conversation that has no proposal, invite or contract. For example, a message sent from the freelancer’s profile or a reply to a boosted profile ad. The event fires once per conversation, for the client’s first message. Later messages in the same conversation don’t trigger it. Getmany detects these conversations through Master Inbox, so the event is only sent for agencies with Master Inbox connected. It usually arrives within about 30 minutes of the client’s message, and messages older than 6 hours when detected are skipped. message.text can be empty while Upwork hasn’t delivered the message text yet, for example when the client only sent an attachment. client.name, client.organizationName, room.name and room.createdAt are omitted when Upwork doesn’t provide them.
Request data sample