Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Confluence Cloud REST API v1 to v2 migration

Edited

We are building an App using REST API v1s. Some of them are deprecating and we have to migrate to v2. For example -

Space API - Space API v1

moving to

Space API v2

Please help me understand -
v2 APIs are a new set of REST APIs with overlapping functionality with v1.

Not all v1s have corresponding v2s.

1. Is there a plan to migrate to v2 for all v1 APIs?

2. What is the experimental tag? I understand v2 having experimental tag but some v1 also have experimental tag. What does experimental tag mean? Are these the APIs that are just under monitor and will eventually mature and stabilize? Do you suggest not using them right now for stable products? 
For ex -
Get Modules API

3. Resiliency is very paramount to our app. Earlier with space API, we were skipping batches in case of bad batch. Cursor now will not allow us to do the same anymore. Do you have suggestions?

 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events