Prototyping information is missing from the REST API

The only information that comes through in the rest API aound prototyping are these three properties:
transitionNodeIDString: Node ID of node to transition to in prototyping
transitionDurationNumber: duration of the prototyping transition on this node (in milliseconds)
transitionEasing - easing type

Everything else is missing:

  • event type
  • transition aninmation/direction
  • positioning of overlays

Also given a node can be given multiple interactions, they would have to be an array.

SO my question is are there plans to include the prototyping information in the REST API?

(Or perhaps I am missing something, and there is a way to do this?)


Yeah me too! That would be extremely useful.

There was a conversation about this a couple of years ago and someone from the team (@Karl_Jiang ) was saying it wouldn’t be too hard to add, but I’m wondering what happened in the meantime.

I dug back up the conversation in the old forum where this topic was being discussed:

1 Like

Any update on this?

1 Like

This piece of API would be crucial, and supposedly also a really small tasks.
According to the previous discussion it has been on the backlog since 2018.
Is there any chance to get this through any time soon?

Any news about that?

I know this is an older thread, but I’d just like to emphasize how awesome getting all prototype information from the rest API would be :slight_smile:

Currently at my job we use the rest API to generate responsive html/css web pages from individual files, which has been really useful into our day-to-day since we manage websites for multiple clients. Unfortunately, since prototyping information isn’t fully serialized in the API response, we are somewhat limited in terms of the interactivity of these generated pages.

Sending the full prototyping information in the response would unlock some really powerful workflows for a lot of designers/developers in similar situations!

1 Like

Any news? Please please please

1 Like