JSON Format for API usage

doublethinker

I am trying to use Zapier to read the RSS of my publishing site so that I can automatically updates to an existing discussion on Flarum. I couldn't find clear examples in the wild beyond https://discuss.flarum.org/d/6236-are-rest-apis-available-for-this-use-case/7

According to the linked thread, it seems that the JSON format to create a new discussion is something like this. Please correct me if I got the structure wrong. It was reverse engineered from the PHP.

// Url: flarum.com/api/discussions
// Headers
Content-Type: application/json
Accept: application/json
Authorization: Token xxxxxxxxxxxxxxxxxxxx; userId=1
{
  "data": [
    "type": "discussions",
    "attributes": {
      "title": "the article title",
      "content": "the content body"
    },
    "relationships": {
      "tags": {
        "data": [
          {"type": "tags", "id": "3"}
        ]
      }
    }
  ]
}

But what I actually need is to create a post in an existing discussion. If I could take a guess, I would think that the JSON would look something like this:

// Url: flarum.com/api/posts
// Headers
Content-Type: application/json
Accept: application/json
Authorization: Token xxxxxxxxxxxxxxxxxxxx; userId=1
{
  "data": [
    "type": "posts",
    "attributes": {
      "content": "the post content"
    },
    "relationships": {
      "tags": {
        "data": [
          {"type": "discussions", "id": "3"}
        ]
      }
    }
  ]
}

Could someone direct me or create an example of the JSON format I need to create a post in an existing discussion? I would prefer to run this through an expert before trying it on Zapier.

*Further to this question. Is the post content sent via JSON processed by the Markdown extension?

EDIT: Amended to reflect @sledov's correction.

sledov

Check how request looks like from "Developer Tools" when you submit it from the browser. See this post for details.

Your JSON is not well formed. JSON uses double quotes.

I don't know about Zapier. Just find a tool that works for you and start playing with it. Here are two suggestions:curl for command line, insomnia if you need a gui client. Try to do it yourself first, ask questions later.

And yes, post body will be processed in a normal way. Including markdown processing.

doublethinker

sledov I considered curl, but the way my site is built (Grav CMS, but using it to periodically generate a static site) makes it preferable to use Zapier as I already I already expose the information I want via RSS feed to Zapier to automatically create social posts.

So data I want is ready, and I have the headers and API key for Zapier to connect to Flarum via GET or POST. The only thing left is the JSON format that Flarum accepts. I thought of trying it first, but it's a literal shot in the dark- hence the outreach.

That's a good tip to find out the attributes I need. Will try it out.

doublethinker

This turned out to be easier than I expected after using the Dev Tools. For those that may stumble upon this:

{
    "data": {
        "type": "posts",
        "attributes": {
            "content": "A new article was published: **{{xxx__title}}** {{xxx__description}} *{{xxx__content}}* Read the full [article]({{xxx__link}})."
        },
        "relationships": {
            "user": {
                "data": {
                    "type": "users",
                    "id": "2"
                }
            },
            "discussion": {
                "data": {
                    "type": "discussions",
                    "id": "5"
                }
            }
        }
    }
}