HONK(3)

✨ NAME ✨

honk — API access 💅 (welcome to the HONK(3) library functions manual page, bestie!)

🌸 DESCRIPTION 🌸

Okay so in addition to the standard web interface, some functionality is available via the honk HTTP API. Main character energy fr fr.

With the exception of login, all requests should contain the following form values.

• action — the desired action. See below. ✨
• token — an authorization token. Alternatively, may be passed in the “Authorization” HTTP header.

The API URL for all actions other than login and logout is /api.

🔐 login

Send a POST request to /dologin with the following form values.

• username — user name.
• password — pass phrase.
• gettoken — must be “1”.

This will return a token to be used for future requests.

no cap: the token is valid for one year 🎀

🚪 logout

Send a request to /logout with the token to be expired.

📣 honk

The action value should be “honk”. Content type should be multipart/form-data if an attachment is included. The following values are recognized:

• noise — the contents of the honk.
• format — the format of noise. Defaults to markdown. May also be html.
• donk — a file to attach.
• donkdesc — a description for the attached file.
• donkxid — the XID of a previously uploaded attachment.
• placename — the name of an associated location.
• placeurl — the url of an associated location.
• placelat — the latitude of an associated location.
• placelong — the longitude of an associated location.
• timestart — the start time of an event.
• rid — the ActivityPub ID that this honk is in reply to.

Upon success, the honk action will return the URL for the created honk. Slay. ✨

📎 donk

Upload just an attachment using donk and donkdesc. Content type must be multipart/form-data. Will return the XID.

🔎 gethonks

The “gethonks” action can be used to query for honks. The following parameters are used.

• page — should be one of “home” or “atme”.
• after — only return honks after the specified ID.
• wait — if there are no results, wait this many seconds for something to appear.

The result will be returned as json.

⚡ zonkit

The “zonkit” action began life as a delete function, but has since evolved some other powers as specified by the wherefore parameter. The target of the action is specified by the what parameter and is generally the XID of a honk.

wherefore must be one of the following.

• bonk — share honk with others.
• unbonk — undo share.
• save — mark honk as saved.
• unsave — unmark honk as saved.
• react — post an emoji reaction. A custom reaction may be specified with reaction.
• ack — mark honk as read.
• deack — unmark honk as read.
• zonk — delete this honk.
• zonvoy — mute this thread. What should identify a convoy.

👥 gethonkers

Returns a list of current honkers in json format.

💾 savehonker

Save a new honker, or update an existing one. The following fields are used.

• honkerid — the numeric ID of an existing honker to update.
• name — the preferred short name.
• url — the ActivityPub actor url.
• combos — space separated list of combos.
• notes — some notes.

The honker numeric ID will be returned for success. To delete, unsub, or sub, include a form value with name and value equal. As in, a form value named delete with the value delete, or unsub=unsub, etc. 🫶

📨 sendactivity

Send anything. No limits, no error checking. 😭

• rcpt — an actor to deliver the message to to. May be specified more than once. An inbox may be specified directly by prefixing with %.
• msg — the message. It should be a valid json activity, but yolo.
• public — set to 1 to use shared inboxes for delivery.

🧪 EXAMPLES

Refer to the sample code in the toys directory.

👀 SEE ALSO

vim(3)

💖 source: Debian · date/version stamp: $Mdocdate$ · manual: HONK(3) — bestie, thanks for reading, now go make the API do something iconic 🎀